FS#24617 - [libreoffice] oosplash.bin eating 100% CPU

Attached to Project: Arch Linux
Opened by Thiago Coutinho (thiagoc) - Tuesday, 07 June 2011, 16:49 GMT
Last edited by Andrea Scarpino (BaSh) - Tuesday, 26 July 2011, 10:24 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Andreas Radke (AndyRTR)
Stéphane Gaudreault (stephane)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 16
Private No

Details

Description:

Open some file in LibreOffice and after some minutes oosplash.bin begin eating 100% CPU. Killing the process solve the issue.

Additional info:

Kernel 2.6.38-ARCH
libreoffice 3.4.0-2
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Tuesday, 26 July 2011, 10:24 GMT
Reason for closing:  Fixed
Additional comments about closing:  libreoffice 3.4.2rc2
Comment by Jelle van der Waa (jelly) - Tuesday, 07 June 2011, 21:20 GMT
This is an 100% upstream bug
https://bugs.freedesktop.org/show_bug.cgi?id=38028
https://bugs.freedesktop.org/show_bug.cgi?id=37600
Comment by LinuxSEAT (linuxSEAT) - Wednesday, 15 June 2011, 17:26 GMT
Comment by Andreas Radke (AndyRTR) - Wednesday, 15 June 2011, 19:04 GMT
Just uploading LibO 3.4.1rc1 to testing. Please give it a try.
Comment by Federico G. (DepreTux) - Friday, 24 June 2011, 18:34 GMT
Same thing with kernel26-lts
Comment by Jelle van der Waa (jelly) - Saturday, 25 June 2011, 07:14 GMT
It's not a kernel problem, it's a bug in libreoffice
Comment by Francisco Pina (Stunts) - Wednesday, 29 June 2011, 21:34 GMT
Appears to be fixed in 3.4.1rc3-1 from testing. (Although on my system I couldn't reproduce the problem every time with 3.4.0)
Can anyone confirm please?
Comment by Andreas Radke (AndyRTR) - Friday, 01 July 2011, 20:16 GMT
Please report with final 3.4.1.
Comment by Francisco Pina (Stunts) - Saturday, 02 July 2011, 11:49 GMT
Seems to be fine with 3.4.1-1 too.
Anyone else can confirm?
Comment by Lyman Li (lyman) - Sunday, 03 July 2011, 08:37 GMT
unfortunately, on my laptop 3.4.1 still consumes one cpu.
Comment by Jelle van der Waa (jelly) - Sunday, 03 July 2011, 10:58 GMT
Just happend here too, a 'dirty' fix is disabling the splash logo in /etc/libreoffice/sofficerc
Comment by nan (someonerandom) - Monday, 04 July 2011, 17:05 GMT
Fixed it by setting Logo=0, too.
Comment by Andreas Radke (AndyRTR) - Monday, 04 July 2011, 18:30 GMT
So far you all report only a "me too". That won't solve it. Report it properly upstream or find out what our pkg breaks it downstream.

The 2 mentioned reports seem to be something different.
Comment by Jelle van der Waa (jelly) - Monday, 04 July 2011, 18:41 GMT
My solution might only work if you launch 'soffice' well this should indeed be reported upstream
Comment by Francisco Pina (Stunts) - Tuesday, 05 July 2011, 11:38 GMT
After further testing, I once again confirm the issue. It only happens after about 20 minutes of use on my laptop, tough.
I have my hands full right now, but I expect to be able to report this upstream tonight if no one else has done it by then.
Comment by nan (someonerandom) - Tuesday, 05 July 2011, 13:59 GMT
Francisco: Maybe this issue is fixed by commit 5553f18bd0b6c19e06b7d9285e4aac54826d2f42 in libs-core. But I hadn't time to check this.
Comment by nan (someonerandom) - Tuesday, 05 July 2011, 16:31 GMT
I did a clean upstream build of 3.4.1 with "./configure --without-system-python --without-junit". With this version and Logo=1 in sofficerc there are no problems. I will make a debug build with the arch package, too.
Comment by Jan (bung) - Wednesday, 06 July 2011, 21:52 GMT
Bug remains in 3.4.1-2...
Comment by Francisco Pina (Stunts) - Wednesday, 06 July 2011, 22:50 GMT
This has been reported upstream quite some time ago actually. And some Arch users are already there.
https://bugs.freedesktop.org/show_bug.cgi?id=37579
We should go offer for testing there.
Comment by Jelle van der Waa (jelly) - Thursday, 07 July 2011, 07:38 GMT
It would really help if you gave them a full backtrace with glib and (gtk?) with debugging symbols, but then you also would have to rebuild libreoffice with debugging symbols (which can take some time )
Comment by Francisco Pina (Stunts) - Thursday, 07 July 2011, 12:10 GMT
Damn, that's a bit too much for my poor laptop right now. I will try to leave it overnight...
Comment by nan (someonerandom) - Sunday, 24 July 2011, 21:30 GMT
With 3.4.2rc2 this should be fixed.

Loading...