Apache OpenOffice (AOO) Bugzilla – Issue 114116
Extension Manager Check for updates window spin loops, Mac OS X
Last modified: 2017-05-20 10:04:41 UTC
After submitting a crash report for the update checker, I noticed that the CPU load for the update window peaked out, even when not crashing. In general this would be considered a defect antithetical to use on portable computers. The poor little Macbook turns into a howler monkey with it's fan screaming and threatening to thermal limit, the cause apparently a spin loop, exacerbated by prolonged times to return an update check due to slow Internet access. Also a threat to battery powered usage. The spin loop is inherent in the update checker regardless of process state (as long as the update checker window is open). Mac OS X 10.6.4 The extension manager is not available without having a document open, checked for both .odp and .odt files, same results with the update checker open.
Sorry, not reproducible with Macbook Pro , MacOSX 10.5.8. The extension manager is avaliable without any doc open, just use the menu Tools/Extension Manager.../Check for updates. Does this still happen after a reboot?
The menubar changes after you dismiss the window for selecting a document type, as in opening a preexisting file, and thanks for the reminder I can also select the Extension before dismissing the document type select window. After a reboot (and why?): Select Tool => Extension Manager No high load Select 'Check for Updates' yields high CPU load. (yes it still happens after a reboot.) I'll try and add two attachments containing the lists of Open Files and Ports from the Activity Monitor for the OpenOffice process. Looking at the difference between them shows font close and a bunch of OpenOffice.org.app libraries open and what looks like a second socket or fifo. I'd expect that any difference between 10.5.8 and 10.6.4 would be in system libraries or the kext plug-in. You can see the Carbon and Cocoa Framework versions have rolled for instance. I'll include the otool -L output against soffice as an attachment in case it sheds any light. The only similar occurrence I've seen was with kicad a Cad tool, the PCB app using libWx (Cocoa). I've been meaning to try and compile it myself. OpenOffice seems a little too big to try as a mere troubleshooting step. I'm using a late 2008 aluminum Macbook (5,1), 32 bit kernel, 10.6.4 with all current updates (excluding iLife09, etc.). I'd accept you either can't confirm the bug or aren't equipped to confirm it. The attached files: open files and ports before check for updates open files and ports after check for updates otool dash L soffice.bin (for system library versions)
Created attachment 71407 [details] open files and port before opening extension update check
Created attachment 71408 [details] open files and port after opening extension update check
Created attachment 71409 [details] ldd equivalent to list versions of system files under OS X 10.6.4
Created attachment 75407 [details] High CPU Load with Extension Update Window Open
Created attachment 75408 [details] CPU Load Drops when Extension Update Window closed
I attached two GIF images showing the effects of having the Extension Update window open on the CPU Load. The first showing the CPU load maxing out, presumably due to a spin loop. The second when the Extension Update window is subsequently closed, in which the load drops to nothing.
Changed component.
Reassigned.
This Issue requires more information ('needmoreinfo'), but has not been updated within the last year. Please provide feedback as requested and re-test with the the latest version of OpenOffice - the problem(s) may already be addressed. You can download Apache OpenOffice 3.4.1 from http://www.openoffice.org/download Please report back the outcome of your testing, so this Issue may be closed or progressed as necessary - otherwise the issue may be Resolved as Invalid in the future.
(In reply to Rob Weir from comment #11) > This Issue requires more information ('needmoreinfo'), but has not been > updated > within the last year. Please provide feedback as requested and re-test with > the the latest version of OpenOffice - the problem(s) may already be > addressed. > > You can download Apache OpenOffice 3.4.1 from > http://www.openoffice.org/download > > Please report back the outcome of your testing, so this Issue may be closed > or > progressed as necessary - otherwise the issue may be Resolved as Invalid in > the > future. There has been no response to this issue since this 2013 assessment. The original report is against an OpenOffice.org release that is not supported by Apache OpenOffice. I am resolving this issue as obsolete. If there remain problems of this kind with the latest versions of Apache OpenOffice (i.e., 4.1.x or later), new analysis and new incident reports should be provided.