Deleting slides is fine. When trying to add 1 new photo ( max size 1024 pixels) Impress tries to Save error message Fatal Error Bad Allocation appears. Presentation has 59 slides all have been resized to 1024 pixels. This is a new problem, it used to work fine, but I think I have updated Impress, am now running 4.3.62 in Windows 8.1. This problem is really serious for me, since I can't update my presentations. Thanks Victoria
It is hard for us to test, if you can't share the problematic file. Could you test with the latest version, 4.4.3, if the problem remains: http://www.libreoffice.org/download/libreoffice-fresh/
"Bad Allocation" the term I get when trying to add slides to an Impress file. I've only got 48 slides and need at least 8-10 more. This happened when only about 25 slides were added, so I did then 10 at a time until I got "bad allocation". Then added 5 at a time until ditto. Then 2 at a time, then one. Now ca't add anything! HELP!! 1. What does "bad allocation" mean? 2. This is VERY FRUSTRATING in LibreOffice - getting error messages that the help site can't or won't recognize. It all too often happens and I usually have to go out to Google Chrome to find an answer. THAT IS POOR! Google didn't really help here.
(In reply to john4070 from comment #2) > "Bad Allocation" the term I get when trying to add slides to an Impress > file. I've only got 48 slides and need at least 8-10 more. > This happened when only about 25 slides were added, so I did then 10 at a > time until I got "bad allocation". Then added 5 at a time until ditto. > Then 2 at a time, then one. Now ca't add anything! HELP!! It is not clear that this is the same problem as the original report. The report description talks about adding a photo and not a slide. In any case we cannot confirm the report or help in any way, if you don't attach an example file. It can simply have some placeholder images as long as the bad allocation thing is consistent. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the document.
*** Bug 92466 has been marked as a duplicate of this bug. ***