oooqs eats 100% cpu

Bug #50136 reported by aexl
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
oooqs (Ubuntu)
Won't Fix
Undecided
Unassigned
oooqs2-kde (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

when i start the openoffice quickstarter, the systray reports 100% cpu usage and soon the noise of my notebook fan becomes louder.
although ooops is a great thing, this bug is a showkiller for mobile usage.
(oooqs 2.0.2 on kde 3.5.2)

Tags: patch
Revision history for this message
aexl (aexl) wrote : Not always reproducible

When i observed this for the first time, i could reproduce it every time. Now, after several reboots and updates i cannot reproduce it any more, but will add info if it does.

Revision history for this message
aexl (aexl) wrote : Send-to-tray

Now i can often reproduce the cpu-eating oooqs.
It appears to come around, when i send to tray my database form.
(as soon as i start oooqs thin wont really work any more.)
Later strange things happen:
- exit oooqs
- kill all oo* and soffice* processes
- start oooqs
->more than ten soffice processes appear and vanish again

Revision history for this message
Marco Cimmino (cimmo) wrote : Re: oooqs eats my cpu

reproduced with kde kubuntu 6.06.1, kde 3.5.5, openoffice 2.0.3-6dapper3, oooqs 2.0.3-7ubuntu2

Revision history for this message
Florian Hackenberger (f-hackenberger) wrote :

Still reproducable with Ubuntu 6.10, please confirm.

Revision history for this message
Florian Hackenberger (f-hackenberger) wrote :

Proposed patch, please review and apply if it solves the problem (it does on my installation). The problem is that openoffice seems to fork new processes repeatedly on start-up and the parents exit() afterwards (shell script wrappers I suppose). oooqs2 connects the void KProcess::processExited signal to the preloadInstance() slot, which checks if a soffice.bin process is running and starts openoffice if not. Unfortunately openoffice takes a while to start-up completely and soffice.bin seems to be one of the processes which are forked later on during start-up (by the openoffice start-up scripts probably). Therefore preloadInstance() thinks openoffice is not running and executes a new instance. I simply delayed the check for 10sec, on receiving the KProcess::processExited signal. Apply and enjoy.

Revision history for this message
Florian Hackenberger (f-hackenberger) wrote :

Ahm...forgot to mention that the patch is for oooqs2-kde in edgy. Please modify the binary package hint, because I can't.

Revision history for this message
Florian Hackenberger (f-hackenberger) wrote :

forgot to check the 'Include attachment' box :-)

Revision history for this message
Florian Hackenberger (f-hackenberger) wrote :

Hmm...I never thought that clicking on the affected package name would let me modify the bug's status...

Changed in oooqs:
status: Unconfirmed → Fix Released
Revision history for this message
Florian Hackenberger (f-hackenberger) wrote :

Now it affects the right package

Revision history for this message
RJ Clay (rjclay) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Changed in oooqs:
status: New → Incomplete
Revision history for this message
Daniel T Chen (crimsun) wrote :

oooqs is no longer shipped post-gutsy.

Changed in oooqs:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.