Created attachment 114336 [details] Sample file created in LibO 4.2 with a light blue shape in the bottom right corner of page that I am not able to re-open in 4.4 When I try to open a Writer document that includes a custom picture as background of page, Writer crashes with a "Bad allocation" error displayed. (e.g. when opening attached document that I successfully created in previous LibO version and that I am ot able to re-open since i upgraded to LibO 4.4) Alternately, if I tried to include a custom picture through the Area Tab of the Page Style dialog selectiong Bitmp and then select a custom bitmap using the "import an image ..." button, I either get a "image non imported" error message or Writer eventually crashes with a "Bad allocation" error message
Unconfirmed with Version: 4.4.2.1 under mint 17.1 x64. File opens normally here. Windows only ?
Just for the test, could you rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile#Windows) and give it a new try?
(In reply to Julien Nabet from comment #2) > Just for the test, could you rename your LO directory profile (see > https://wiki.documentfoundation.org/UserProfile#Windows) and give it a new > try? I already tried this workaround without results and retried once more this morning with no more luck : a) opening a file with a backgrounf picture end in a "Bad allocation" Fatal Error message and a freeze of LibO b) when trying to include a custom picture as background through the Area tab of the Page Style dialog, I am able to see it appear. However, when trying to save the document, it aborts with the same "Bad allocation" fatal error message and a freeze of LibO I highlight that these freezes often generate an error message when restrarting LibO stating that there is a problem with Java Environment (Installed is JRE 1.7.0_71 which is the last version applicable to Windows XP)
Thank you for your feedbacK. Do yo use Java 32 bits? Indeed, if you have LO 32 bits, you must have Java 32 bits. Also, again for the test, you can give a try to prerelease 4.4.2RC
(In reply to Julien Nabet from comment #4) > Thank you for your feedbacK. > > Do yo use Java 32 bits? Indeed, if you have LO 32 bits, you must have Java > 32 bits. > Also, again for the test, you can give a try to prerelease 4.4.2RC I confirm that JRE used is 32-bit. I installed LibO 4.4.2.1. Using this version does not allow me to open existing file without the "Bad allocation" Fatal Error message that crashes LibO. However, I had been able to get one step further and successfully save a new document to which I added a Background picture that appeared on it. I had been able to re-open it without any error displayed ... but unable to save it again after modification : "Bad allocation" message popped up
Thank you again for your feedback A backtrace would be useful, so I put "want-backtrace", hoping that someone would provide one. If interested about this, you can give a try by using this link: https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_How_to_get_a_backtrace
It's working well in Windows 7 64bit with LibreOffice Version: 4.4.1.2
Created attachment 114466 [details] Attempt for Backtrace thru WinDbg This is the file generated from WinDbg but it catches no error :(
(In reply to Julien Nabet from comment #6) > Thank you again for your feedback > > A backtrace would be useful, so I put "want-backtrace", hoping that someone > would provide one. > If interested about this, you can give a try by using this link: > https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows: > _How_to_get_a_backtrace I added a Backtrace generated from the steps described in above link but I am afraid it is incomplete as WinDbg remains *BUSY* when the "Bad allocation" message popped up. I then tired to click the OK button on it and WinDbg eventually gets idle but the "!analyse -v" command did not catch any error analysis :(
Ok, let's hope someone will be luckier than you.
I opened the file with 7zip and pulled out the file 100002010000136100001B6843E93F8A.png, which is 4961 x 7016, and dragged it into a new document. soffice.bin memory is up to 314MB. If I import it as page background then it is up to 322MB. Scrolling the document causes memory to jump up into the 400 to 500 range. I also noticed on the original file that the image disappears off the bottom of the page. Version: 4.4.1.2 Build ID: 45e2de17089c24a1fa810c8f975a7171ba4cd432
Created attachment 114557 [details] backtraces backtrace: 1. Tools → Options → Advanced → Use a Java runtime environment is unchecked. 2. Click on Image1, the schematic. 3. Right Click → Image. 4. Macro tab → No to Java → Macro from → open up document and click on Standard → Cancel. 5. Tools → Macros → Organise Dialogs → Close. 6. Close Document. Result: LibreOffice Document Recovery. Due to an unexpected error, LibreOffice crashed. backtrace2: Trying to document the above in another document, I copied the the steps to paste here. I forgot what the Organise Dialog was called so went back into it, then closed it. Brought up Help -> About and copied Version and Build ID and closed that dialogue and that caused a crash. They look like the same error, but not what we were looking for. Version: 4.4.1.2 Build ID: 45e2de17089c24a1fa810c8f975a7171ba4cd432
Created attachment 114558 [details] screenshot of index table preview I also noticed this.
Ignore comment 12. I reported it on bug 90423.
Comment on attachment 114557 [details] backtraces Following comment 14 indicating to ignore comment 12, these bts shouldn't be taken into account.
Windows 10 Pro, Version 1511 (OS Build 10586.36) Version: 5.0.4.2 Build ID: 2b9802c1994aa0b7dc6079e128979269cf95bc78 Locale: de-DE (de_DE) I also can't reproduce any of the described behaviour. Since it's been some time and the error couldn't be backtraced/reproduced by anyone I'm changing the status to RESOLVED WORKSFORME.