It is a 556Mb presentation, opening it carouses a
General input/output error
LO closes itself.
Unconfirmed with v188.8.131.52 under mint 17.2 x64.
On other Windows 10 computer with LO 184.108.40.206 I get:
Unconfirmed with v220.127.116.11 under windows 10 x64.
Can you reset the user profile to see if that helps ?
Eugene Savitsky 2015-11-12 00:30:09 UTC
This attempt was on a brand new computer, freshly installed Win10 x64 and LO.
There is nothing to reset.
I will update LO on the second computer and try again.
No repro Version: 18.104.22.168.alpha1+
Build ID: 4b918705f67d0837b56e56d7abac23e6eb21feb4
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2015-11-12_00:33:46
Opened without error with:
Win 7 Pro 64-bit, Version: 22.214.171.124 (x64)
Build ID: e5f16313668ac592c1bfb310f4390624e3dbfb75
Locale: fi-FI (fi_FI)
You are for sure using the 64-bit version of LibreOffice as well? Just thinking of memory use..
Maybe you could also try a build of 5.1: http://dev-builds.libreoffice.org/daily/master/Win-x86_64@62-TDF/
It will install separately, it will not overwrite your 5.0.
http://www.libreoffice.org/download/libreoffice-fresh/ - it gives me the x86 version by default, as well as for all average user. So, I have the x86 version installed.
(In reply to Eugene Savitsky from comment #7)
> http://www.libreoffice.org/download/libreoffice-fresh/ - it gives me the x86
> version by default, as well as for all average user. So, I have the x86
> version installed.
Ok, you could try the 64-bit version then http://www.libreoffice.org/download/libreoffice-fresh/?type=win-x86_64&version=5.0
Checked 5.1 alpha 1 x64 - OK. Opened and working.
On x86 it is opened and after a 3-5 seconds closes with error.
(In reply to Eugene Savitsky from comment #2)
> On other Windows 10 computer with LO 126.96.36.199 I get:
> Fatal error
> Bad allocation.
Ah yes, I got this also with a 32-bit 5.1 build. I got it after scrolling the slide list a bit.
Let's set to NEW.
Win 7 Pro 64-bit Version: 188.8.131.52.alpha1+
Build ID: b216cc1b8096eb60c27f67e8c27b7cd756c75e38
TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-11-12_00:06:20
Locale: fi-FI (fi_FI)
** 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)
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!
I test it with 184.108.40.206-64 on win10-64
So it is a LOO 32-bit problem only like the other users.
Fail with 556 MB compressed file size in view the 2-GB-Limit in 32-bit version of internal uncompressed pictures is quite normal. And 4 GB is the hard limit of every 32bit-process with 64-bit machines. In Windows 32bit it is normally 2 GB the limit.
Possible workaround with great files:
you can change in options -> memory -> picture memory and object memory and number of objects should increased.
Real memory should be more than 4GB to have full free 4 GB with LOO 32-Bit for maximal performance and possible size of files.
LOO 32bit should send a message, if the file is too huge.
x86 LO 6.1.3 in Windows opens the file, albeit very slowly. Memory on scroll rises to 1,3 GB and then LO crashes with Fault Module Name: ucrtbase.DLL.