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


I have a strange problem with the new LO 5.1 on Mac OS X Yosemite (10.10.5). I installed it and 
started it up for the first time. Naturally the first time the app gets verified. However the 
verification took a long time and my computer got almost completely unresponsive. 

Activity Monitor indicated that kernel_task had growm to more than 6.3GB (real memory). My machine 
has 8GM memory. It did not take very much CPU time, but everything came virtually to a halt. Even 
the clock sometimes lagged minutes behind. The verification process took more than 2 hours and 15 
minutes, after which I had to leave. When I returned it had finished, so I know it took less than 5 
hours. Ater confirming that I wanted to run the application downloaded from the internet, LO 
continued, but it took at least 10 minutes before it appeared. In the meantime the kernel_task 
memory footprint still was high, but later it dropped back to more reasonable values.

I did this twice, with a reboot in between. The reboot didn't solve the problem.

I also tried LO 5.0.5, and its verification took about 5 minutes (still quite long I think), with 
kernel_task going up to about 4GB. But at least the system continued to work normally.

So what can be the problem with LO 5.1?
-- 
Piet van Oostrum <piet@vanoostrum.org>
WWW: http://pietvanoostrum.com/
PGP key: [8DAE142BE17999C4]


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.