"Bad Allocation" is the error I get when trying to add photos to an Impress presentation of 51 slides, 75,508 KB size. I only want to add about 5 more. I've made considerably bigger programs in the past. What's wrong and how can I fix it? I'm using an ASUS PC with plenty of RAM and other memory. Thanks MUCH! --John
Please report your LibreOffice version (from Help - About LibreOffice) Example: Version: 4.4.3.2 Build ID: 4.4.3.2-6.fc22 Locale: en_GB And your operating system version Examples: Win7 x64 Pro or Ubuntu 15.04 x64
Sorry I missed you have filled that. I can't reproduce that. Version: 4.4.3.2 Build ID: 4.4.3.2-6.fc22 Locale: en_GB OS: Fedora 22
Please try, if updating to LibreOffice 4.4 has any effect. If the crash occurs in 4.4, too, you could get a backtrace: https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg I'm assuming you can't share the presentation publicly. It would be great for testing, if you could, though :) Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team
I had the same error after adding 218 photos to a newly created presentation. Very little else in it apart from a few short text elements. The error occurs similarly on LO 4.4.7 on Mageia 5, as with the same odp file in LO4.3 on Windows 10. On Windows 10 i tried to minimize the presentation, but this resulted in a hanging process. i doubt I can attach this odp here as it is 998Mb. But I can post it somewhere on the net, provided I can pass the location by e-mail. There is nothing wrong with the photos I try to add to this odp, as I have been able to insert these in a new odp. I can provide these as well if needed.
This is causing big problems for me; a presentattion I created in 2007 (with OO) and saved in odp in 2011, now plays very badly0 It contains some 380 (but lighter in size) photos. Somewhere halfway, LO just shows random colors for some 40 slides. I can provide this odp as well if needed. I installed LO5.0.4 on Windows 10, and this one allows me at least to save one change on the odp I reported first. Continuing testing......
Used my presentation on LO 5.0.4 on Win 10: all slides show correctly in editing and "show" mode, and I was able to do changes and save te file. Trying to do the same in LO 5.0.4 on Mageia 5: slides slow OK in the preview pane up to slide 192, but selecting slide 183 gives a empty screen in the editing pane (the small icon for the presence of a graphical file shows, nut not the actual image). The slide show gives already up at slide 13, so it behaves even worse than LO 4.4.7
I see this problem with most of my presentations since I upgraded to Libreoffice 5.1* One presentation that causes this "bad allocation" error can be obtained here https://www.dropbox.com/s/zyxssgpva8f4ns4/2015-05-25%20Nonequilibrium.odp?dl=0 The error shows up in LO 5.1.2.2, on Windows 10 64bit The same problem does not show up with older versions of LO (Before upgrade I had 5.0) or with OO.
So how much memory exactly do you guys have? I have 32 GB and I have no problems when adding images to Juanjo's file (which btw. could be uploaded as an attachment as it is under 10MB). Arch Linux 64-bit, KDE Plasma 5 Version: 5.2.0.0.alpha1+ Build ID: 540fee2dc7553152914f7f1d8a41921e765087ef CPU Threads: 8; OS Version: Linux 4.5; UI Render: default; Locale: fi-FI (fi_FI.UTF-8) Built on April 30th 2016
NeedInfo as of Comment 9. After answering that question and adding a test file, please set the bug back to Unconfirmed.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20170131
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20170301