Bug 83846 - "Bad allocation" on Windows 7 x64 when working with master document
Summary: "Bad allocation" on Windows 7 x64 when working with master document
Status: NEEDINFO
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Presentation (show other bugs)
Version: 4.3 Daily
Hardware: x86-64 (AMD64) Windows (All)
: high major
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-14 14:09 UTC by Darius Daniel Grigoras
Modified: 2015-01-17 13:12 UTC (History)
5 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Darius Daniel Grigoras 2014-09-14 14:09:16 UTC
Hi 

I work with a master document and I found out that I have to run LibreOffice on Ubuntu x64, as on Windows 7 x64 LibreOffice returned "Bad allocation" and crashed each time I inserted many or all of the subdocuments, which amount to 2000 pages. On Ubuntu it runs great, but on Windows 7 x64 poorly. I have to add that I also have OpenOffice installed, but I understand that there shouldn't be any conflicts by having both installed.

Also, at the subdocument level, and this again on Windows 7 x64, LibreOffice would just not show some of the larger pictures contained by a 40 MB subdocument.
Comment 1 Jean-Baptiste Faure 2014-09-14 20:19:53 UTC
Not sure if the bug is in LibreOffice ;-)

What amount of RAM do you have under W7 ?
Did you play with graphic cache parameter : menu Tools > Options > LibreOffice > Memory ?

Set status to NEEDINFO. Please set it back to UNCONFIRMED once you have provided requested informations. Thank you for your understanding.

Best regards. JBF
Comment 2 Julien Nabet 2014-09-15 19:57:26 UTC
Another thing to have in mind, LO is build on 32 bits only on Windows so even if you're on Win7 64 bits, you might have some limitations.

What's the physical size of your whole doc (master and subdocuments)?

Now there are still memory leaks fixed on LibreOffice. For the test, you may give a try to daily master sources, see http://dev-builds.libreoffice.org/daily/master/Win-x86@51-TDF/current/
Comment 3 Darius Daniel Grigoras 2014-09-16 09:06:51 UTC
My system is equipped with a Core i7-4770, 256GB SSD, 8GB of RAM and runs Windows 7 x64.
The total size of the subdocuments is 114 MB, and growing.

I have set the memory setting for LibreOffice to the maximum allowed and I still receive "Bad allocation" in just a few seconds after inserting the subdocuments into the master document.

As mentioned before, this is not an issue on Ubuntu. I can only work on Ubuntu because of this.
Comment 4 Julien Nabet 2014-10-13 18:43:03 UTC
Following your last comment I put it back to UNCONFIRMED.
Comment 5 Darius Daniel Grigoras 2014-10-14 06:53:06 UTC
(In reply to Julien Nabet from comment #4)
> Following your last comment I put it back to UNCONFIRMED.

Why would you do that? This is a real issue.
Comment 6 Darius Daniel Grigoras 2014-10-14 07:00:33 UTC
I remember creating a sample master doc a while ago, which you can download from here:
https://www.dropbox.com/s/vz43d9x0v1t3fxr/master_for_support.zip?dl=0
Comment 7 Jean-Baptiste Faure 2014-10-14 10:39:53 UTC
(In reply to Darius Daniel Grigoras from comment #5)
> (In reply to Julien Nabet from comment #4)
> > Following your last comment I put it back to UNCONFIRMED.
> 
> Why would you do that? This is a real issue.

Perhaps but you can't confirm your onw bug reports. Each bug report must be confirmed independently.

Best regards. JBF
Comment 8 Joel Madero 2014-10-23 01:37:48 UTC
Also not a blocker - blockers are reserved for truly cases where the vast majority of users would be affected, as we as of now have a single unconfirmed case....not meeting this criteria. Setting to Major - High. 

What are the exact steps to reproduce? Just download the document and watch a memory leak?
Comment 9 Beluga 2014-11-15 12:12:04 UTC
Opens fine here on a system about half as powerful as the reporter's.

Win 7 64-bit Version: 4.4.0.0.alpha2+
Build ID: b021b5983c62e266b82d9f0c5c6d8d8900553827
TinderBox: Win-x86@39, Branch:master, Time: 2014-11-12_01:10:08
Comment 10 Robinson Tryon (qubit) 2015-01-17 10:16:07 UTC
(In reply to Joel Madero from comment #8)
> What are the exact steps to reproduce? Just download the document and watch
> a memory leak?

Darius:

1) Can you still reproduce the problem with 4.4.x and/or 4.5.x builds?

2) As Joel asked, could you be a bit clearer about what steps are required to reproduce the problem?

Status -> NEEDINFO

(Please change status back to UNCONFIRMED after you test with 4.4.x and/or 4.5.x, and provided simple steps for reproduction. Thanks!)
Comment 11 Julien Nabet 2015-01-17 13:12:28 UTC
Darius: for the test, could you rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile#Windows) and give it a new try?


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.