I prepare regulary presentations with Libreoffice. The presentations are not too large (50 - 300 MB) but contain (obviously) a lot of picture, most of them in JPG Format. On a very frequent basis (like 50 times a day) Libreoffice crashes - When adding pictures - When copying multiple pages with pictures - When saving - When "save as" - When "reduce size of presentation" It basically makes the program unusal. Furthermore, the repair function removes a number of pictures which have to be readded everytime. Secondly, Libreoffice looses pictures after saving. The connection is broken and only spaceholders are shown. When pictures have shadows, often only the shadows are shown. After adding a couple of pictures, typically "filter not found" is shown (which happens by the way also in writer). I have to close soffice.bin and restart to add more picture. It seems to get worse with every version. Sometimes "Bad Allocation" is shown, various library not found messages (more seldom but never twice the same), and sometimes you can even select menus, but cannot do anything anymore (save, close, move pictures...). Sometimes it just closes without comment. I was bearing for it since OpenOffice 1.0 for a long time, but it seems as this problem never gets addressed, this is why I file the bug report now.
(In reply to comment #0) > I was bearing for it since OpenOffice 1.0 for a long time, but it seems as > this problem never gets addressed, this is why I file the bug report now. Please be advised that this report won't help to solve it neither without precise steps to reproduce for every issue (you reported a lot of them here - general rule is 1 bug = 1 report). Also attaching 50-300 MB file is not possible. Therefore please split this report into separate issues (if they are not filed already) and help the project by providing backtraces when LibreOffice crashes for each of them. This will confirm the bugs and help to pinpoint where are the problems. Using WinDbg is not a black magic and will help a lot potential developers. Additional read: https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg Also please do not forget to attach precise info about your system and LibreOffice configuration. Maybe some problems are specific to your environment or settings. Last but not least please remember that LibreOffice is powered by a team of volunteers and good bug reports help tremendously in making the fixing process go smoother.
Thank you for your comments. Due to IT restrictions I may not install a debugger in any case. However, it is very simple to reproduce the behaviour: - Save a large presentation - Typically at this point one or two pictures have vanished, i.e. only a placeholder is shown - Save again - LibreOffice Impress crashes with "Bad Allocation" Similar: - Drag and Drop pictures in the presentation (JPG or PNG) - After 4 or 5 typically a message "Filter not found" is displayed - Now other pictures have vanished - Click around in the slides or save - Impress crashes with "Bad Allocation" Similar: - Do a "Compress Presentation" with a large presentation (starts usually around 100 MB) - Compression hangs There are some faults usually happening in the listed order/frequence: 1. "Bad Allocation" with closing of Impress 2. Program hangs 3. Random Error Message and Program closes The repair function typically looses a couple of images after repair. Other ways to reproduce: - Copy a large presentation - Move slides from one presentation to another by drag and drop - "Bad Allocation" or silent close of the program The crashes are very, very obivous. For a number of version similar things happend very frequently in Writer files when adding a larger number of images (typically JPEG), then the import dialoge for a file pops up instead of including the images. I believe this is ONE bug, not several, as it happes in all office parts. From what I see I believe that there is a serious memory handling problem with the import filters, which seem to be used for all parts. As those bugs got worse in the forthcoming of StarOffice/OpenOffice/LibreOffice during its OpenSource live, I was giving good faith that Developers can impossibly miss it. However, having seen that currently between each versions are differences in stability (the one used below is worse as the version before). My tested configurations are - Windows 7 X64 Professional and Home Premium - Intel Core I7 and i5 - 8GB Ram - Discs between 500 and 1000 MB - Some configurations with SSD - All service packs included - Files access locally and via network
Hi Thorsten, Is it OK to mark this party as duplicate of bug 46447 ? Thanks, Cor
Hi Cor, this might well be. From my experience however the files do not vanish mandatory. If you close and reopen the file (make sure not to save!) it happens irregularily that some of the images reappear and others vanish. Some of them are in the file still existing, somethimes they are lost. I am pretty sure the problem is in the filters as this is pretty persistent over all OpenOffice and LibreOffice versions when handling files with lots of pictures. In Impress however, this is basically making it unusable. In Writer it is pretty annoying but usually there are less pictures involved. It seems to be even worse currently, I just spend three full days just getting a presentation that worked ready and could only succeed by giving up and removing slides, exporting to PDF and using the PDF for presentation. The Impress file did never show up completly again. BTW: when exporting to PDF Impress tends to crash on the second export, too, so it very much seems as a general problem with filters. Cheers T
Created attachment 104055 [details] backtrace info when exporting an impress odp to PDF
Created attachment 104056 [details] odp test file
Created attachment 104057 [details] Computer details used
It got stuck when exporting to PDF....
Comment on attachment 104056 [details] odp test file Download from this link: https://drive.google.com/folderview?id=0B1WCyZarWspXRzVBU01OOGtFVzQ&usp=sharing
Exported that Google Drive hosted odp to pdf just fine. Changing to UNCONFIRMED. Win 7 64-bit Version: 4.5.0.0.alpha0+ Build ID: b144f0ac8695dd62a2053b4e88212d0b109c9a41 TinderBox: Win-x86@51-TDF, Branch:MASTER, Time: 2014-11-25_00:14:54
LO 4.3.4, win7. I can export presentation from comment 9 to PDF without crash. I used this presentation and added new pictures and I can confirm "Bad allocation" warning and crash. Steps to reproduce - open presentation from comment 9 - menu Insert -> Picture -> Photo album - select lots of photographs - import -> "Bad allocation" warning and crash
Hi All, I was working for some days on a report were most of my time was waiting for LibreOffice recovering from the image bugs. Today, I upgraded during work to the latest release 4.3.5 and tell you what: I am very, very happy. The bug is quite seldom. Not vanished, but seldom. I could work all day on the report, copy, past, move etc. graphics, between files etc. without a single crash. The bad news: It is not gone. After moving more graphics from one file to another (the session with the files was open all day) and when finally exporting to PDF - Bad Allocation error. If worked after recovering, although the last changes before crash were not saved. If the bug is restricted to PDF Export, I may get around it by using a PDF printer, but it would be nice if that one gets fixed, too. I would love to send you the test document, but due to the confidential nature this will not be possible...
*** Bug 90715 has been marked as a duplicate of this bug. ***
*** Bug 90196 has been marked as a duplicate of this bug. ***
Tried on win7, LO . Can load doc from comment 9, can export to PDF, all content there. Added slides and pics, works well. Used slidesorter to rearrange, works well. Changed slides toobar width (to make re-render slides, you can see one after the other getting sharp), woorks well. Same with slide sorter. Used slideshow and presenter in various modes, works well. Used save as (takes time), worked well. Used reaload, works well. Ended office, crash in the debugger (not visible without). Office restart, load, export PDF, works well, no data lost. It may be that with the 32bit versions (e.g. win) there was a problem in-between with graphics swapping in/out, not too long ago, but that is fixed. @thorsten: Did you use a 32bit version of LO? Have you tried a current version (5)? Have you tried the 64bit win version?
@Armin: I am using LO under windows installing whatever I am downloading when going to the homepage. I don't see if it is X32 or X64, but I would suppose it is the 32bit version. Currently using 5.0.2 which is somewhat more stable, but still crashes quite frequently.
(In reply to thorsten.brandau from comment #2) > My tested configurations are > - Windows 7 X64 Professional and Home Premium > - Intel Core I7 and i5 > - 8GB Ram > - Discs between 500 and 1000 MB > - Some configurations with SSD > - All service packs included > - Files access locally and via network Maybe superfluous question: did you try with a fresh user profile? Any influence from setting of Tools > Options > General > View .. Hardware acceleration and alike (?) More memory .. Tools > Options > General > Memory ? thanks! Cor
@Cor: Yes, several times. Depending on the version it gets worse or better. But it never goes away.
(In reply to thorsten.brandau from comment #18) > Yes, several times. Depending on the version it gets worse or better. But it > never goes away. Several times what ?
@cor New profile, change of acceleration settings, increasing memory settings, change number of objects to keep in memory.... tried to tweak around here quite a bit. Problems are on different machines (windows, linux) pretty much alike with the documents we work here with. Although the linux version seems to be more stable.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
Works for me in Impress Version: 5.1.6.2
raal: you were able to reproduce the crash in comment 11. Is it gone for you now?