Bug 37850 - Libreoffice crashes regularly after resuming data entry after an idle period (5 mins or more)
Summary: Libreoffice crashes regularly after resuming data entry after an idle period ...
Status: CLOSED NOTOURBUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
3.3.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Björn Michaelsen
URL:
Whiteboard:
Keywords:
: 33025 35424 40766 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-06-02 04:08 UTC by Jack Knight
Modified: 2011-12-24 04:27 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
gdb backtrace and all thread backtrace (4.12 KB, application/zip)
2011-06-26 09:39 UTC, cdr.devinov
Details
gdb backtrace taken from 10.10 (mint), 64bit (16.27 KB, text/plain)
2011-07-28 08:10 UTC, Jack Knight
Details
valgrind taken from 10.10 (mint), 64bit (2.12 MB, application/x-bzip)
2011-07-28 08:11 UTC, Jack Knight
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jack Knight 2011-06-02 04:08:20 UTC
If I leave LibreOffice with a document open for a while (doc, calc, any type), then resume typing in that document, it immediately crashes. 

LibreOffice 3.3.2 
OOO330m19 (Build:202)
tag libreoffice-3.3.2.2, Ubuntu package 1:3.3.2-1ubuntu2~maverick1


uname -a
Linux will 2.6.35-28-generic #50-Ubuntu SMP Fri Mar 18 18:42:20 UTC 2011 x86_64 GNU/Linux

dmesg output:
[24354.244064] soffice.bin[4180] general protection ip:7fa9d70d9f0e sp:7fff592c1a80 error:0 in libuno_cppuhelpergcc3.so.3[7fa9d70ba000+9e000]

From postings it seems this also affects 32 bit users and is not specific to LO either. It was happening to me on OOO before I migrated.
Comment 1 Don't use this account, use tml@iki.fi 2011-06-02 07:18:40 UTC
Ubuntu specific, for Björn?
Comment 2 Jack Knight 2011-06-02 08:05:45 UTC
Just to clarify: by IDLE I mean not using LO application - I go off and do other tasks on other apps. Then when I come back and resume typing into LO it crashes. Other apps all remain stable.
Comment 3 cdr.devinov 2011-06-26 09:39:40 UTC
Created attachment 48444 [details]
gdb backtrace and all thread backtrace

remember the bug : work sometime on OOo, then do something else, come back after a while on OOo -> crash (sometime). or do CTRL+s after having spent sometime on other stuff -> crash(sometime).

From my past experience, this kind of bug started first with the version 3 of openoffice. a try with IBM lotus symphony was resulting in the same crash!!!
finally I though libreoffice was not affected... but that is not the case.

I use ubuntu 10.10 (32b) when the problem started with compiz. (disabling opengl for OOO doesn't affect the bug).
I now have on ubuntu 10.10 libreoffice 3.1 and it seems not to be affected by this bug (I was not able to reproduce it).
I also recently got Ubuntu 10.04.... libreoffice 3.3 crash... 3.4 also!!!
The backtrace seems explicit... the trouble come from uno, ure. Except that is a .net like stuff, I have no more idea how it works, and what part it play in Libreoffice, OOo or lotus symphony.

However it seems related to file io with an exception badly uncatched prducing a SIGSEGV.

My guess is that this bug should be redirected to uno framwork. Also ubuntu distro might also play a role in it.

If you need testing for this bug, I have a document (but professional, not to share) that seems to trigger the bug almost garanted within an hour.
Comment 4 cdr.devinov 2011-06-26 13:25:49 UTC
(In reply to comment #3)
> Created an attachment (id=48444) [details]
> gdb backtrace and all thread backtrace
> 
> remember the bug : work sometime on OOo, then do something else, come back
> after a while on OOo -> crash (sometime). or do CTRL+s after having spent
> sometime on other stuff -> crash(sometime).
> 
> From my past experience, this kind of bug started first with the version 3 of
> openoffice. a try with IBM lotus symphony was resulting in the same crash!!!
> finally I though libreoffice was not affected... but that is not the case.
> 
> I use ubuntu 10.10 (32b) when the problem started with compiz. (disabling
> opengl for OOO doesn't affect the bug).
> I now have on ubuntu 10.10 libreoffice 3.1 and it seems not to be affected by
> this bug (I was not able to reproduce it).
> I also recently got Ubuntu 10.04.... libreoffice 3.3 crash... 3.4 also!!!

OOOps, mistake in ubuntu version
read Ubuntu 10.04 as 11.04, sorry...
Comment 5 Jack Knight 2011-07-28 08:07:23 UTC
gdb backtrace and valgrind from 10.10 (Mint) 64 bit.
Comment 6 Jack Knight 2011-07-28 08:10:27 UTC
Created attachment 49669 [details]
gdb backtrace taken from 10.10 (mint), 64bit

2.6.35-22-generic #33-Ubuntu SMP Sun Sep 19 20:32:27 UTC 2010 x86_64 GNU/Linuxlibreoffice-core                      1:3.3.2-1ubuntu2~maverick1
Comment 7 Jack Knight 2011-07-28 08:11:07 UTC
Created attachment 49670 [details]
valgrind taken from 10.10 (mint), 64bit

2.6.35-22-generic #33-Ubuntu SMP Sun Sep 19 20:32:27 UTC 2010 x86_64 GNU/Linuxlibreoffice-core                      1:3.3.2-1ubuntu2~maverick1
Comment 8 Yaron Sheffer 2011-07-31 14:56:52 UTC
I am seeing the exact same behavior for many months, also since OOo. I have previously submitted two gdb traces which might be useful to people debugging this issue - below.

I am seeing this issue both in Writer and Impress very often, and it makes working with these applications extremely unpredictable and unpleasant. Maybe 50% of the times I start the application, I need to go through document recovery first.

https://bugs.freedesktop.org/show_bug.cgi?id=35424
Comment 9 Björn Michaelsen 2011-09-23 11:16:43 UTC
not really an libreoffice bug, but an issue with encrypted home/swap.
Comment 10 Björn Michaelsen 2011-09-23 11:17:35 UTC
*** Bug 35424 has been marked as a duplicate of this bug. ***
Comment 11 Björn Michaelsen 2011-09-23 11:19:16 UTC
(see https://launchpad.net/bugs/745836 for details)
Comment 12 Björn Michaelsen 2011-09-23 11:20:32 UTC
*** Bug 33025 has been marked as a duplicate of this bug. ***
Comment 13 Björn Michaelsen 2011-09-23 11:41:39 UTC
*** Bug 40766 has been marked as a duplicate of this bug. ***
Comment 14 Björn Michaelsen 2011-12-24 04:27:26 UTC
closing