Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index

Re: [tdf-discuss] memory leak in 4.0


On 05/03/2014 22:55, edo1 wrote:
LO 4.2.0 is showing a memory problem that's making it unusable. When I open a
file in it, the RAM usage starts to climb until LO locks up. I get "Fatal
Error osl:Thread:create failed."

After LO has pushed the RAM use to  3.9GB  & frozen I must close it
completely, i.e., kill the processes swriter.exe *32, soffice.bin * 32.
&soffice.exe *32

Things that haven't helped:
        increasing paging size
        repairing LO & helpfile in Control Panel
        running in a clean boot
        
I don't recall this problem occurring in LO 4.1, the previous version I was
running. My box is a Dell 530s, Intel E2500 CPU at 2.5GHz, 4GB RAM.

I sure hope someone can help me get beyond this problem; I'm not getting any
work done. - edo1


I would strongly advise NOT to use 4.2.x at the moment for real-life or important work. Let's say that the "stable branch" right now is 4.1 with its fifth correcting release (4.1.5).




--
To unsubscribe e-mail to: discuss+unsubscribe@documentfoundation.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.