Apache OpenOffice (AOO) Bugzilla – Issue 14765
Crash (core dump) while writing in the word processor
Last modified: 2004-04-05 10:05:06 UTC
This is a backtrace from a crash happening on Solaris 8. I was typing text in the wordprocessor when OO suddenly started autosaving the document and put up the message about an unrecoverable error and exited. The document is very simple, consists of about 50 pages of text with a few tables. No OLE or graphics. I can not reproduct this problem with the same document. (gdb) bt #0 0xff369764 in __sigprocmask () from /usr/lib/libthread.so.1 #1 0xff35e978 in _resetsig () from /usr/lib/libthread.so.1 #2 0xff35e118 in _sigon () from /usr/lib/libthread.so.1 #3 0xff361158 in _thrp_kill () from /usr/lib/libthread.so.1 #4 0xfe54ba24 in raise () from /usr/lib/libc.so.1 #5 0xfe535944 in abort () from /usr/lib/libc.so.1 #6 0xff1a690c in CallSystemHandler () from /tools/openoffice/1.0.3/program/libsal.so.3 #7 0xff1a6a68 in SignalHandlerFunction () from /tools/openoffice/1.0.3/program/libsal.so.3 #8 0xff36b82c in __sighndlr () from /usr/lib/libthread.so.1 #9 <signal handler called> #10 0xff369764 in __sigprocmask () from /usr/lib/libthread.so.1 #11 0xff35e978 in _resetsig () from /usr/lib/libthread.so.1 #12 0xff35e118 in _sigon () from /usr/lib/libthread.so.1 #13 0xff360954 in thr_sigsetmask () from /usr/lib/libthread.so.1 #14 0xff369250 in sigprocmask () from /usr/lib/libthread.so.1 #15 0xfe54e898 in sigrelse () from /usr/lib/libc.so.1 #16 0xfe5358f4 in abort () from /usr/lib/libc.so.1 #17 0xfeaa461c in __1cH__CimplMex_terminate6F_v_ () from /usr/lib/libCrun.so.1 #18 0xfeaa5d9c in _ex_rethrow_body () from /usr/lib/libCrun.so.1 #19 0xfeaa6148 in __1cG__CrunRex_chk_unexpected6F_v_ () from /usr/lib/libCrun.so.1 #20 0xf8a04b68 in __1cJShellExecHexecute6MrknDrtlIOUString_4l_v_ () from /tools/openoffice/1.0.3/program/libsyssh.so #21 0x2141c in __1cHDesktopJException6MH_H_ () #22 0xfebe6dc0 in __1cXImplVCLExceptionHandlerGsignal6MpnNoslSignalInfo__nDvosOOSignalHandlerNTSignalAction__ () from /tools/openoffice/1.0.3/program/libvcl641ss.so #23 0xff1a6798 in CallSignalHandler () from /tools/openoffice/1.0.3/program/libsal.so.3 #24 0xff1a6a38 in SignalHandlerFunction () from /tools/openoffice/1.0.3/program/libsal.so.3 #25 0xff36b82c in __sighndlr () from /usr/lib/libthread.so.1 #26 <signal handler called> #27 0xf9d74da8 in __1cJSwViewImpSRefreshScrolledHdl6MpnFTimer__l_ () from /tools/openoffice/1.0.3/program/libsw641ss.so #28 0xfebe7ad8 in __1cVImplTimerCallbackProc6F_v_ () from /tools/openoffice/1.0.3/program/libvcl641ss.so #29 0xfed42d70 in __1cHSalXLibMCheckTimeout6Mb_b_ () from /tools/openoffice/1.0.3/program/libvcl641ss.so #30 0xfed43170 in __1cHSalXLibFYield6MC_v_ () from /tools/openoffice/1.0.3/program/libvcl641ss.so #31 0xfebe3e90 in __1cLApplicationFYield6F_v_ () from /tools/openoffice/1.0.3/program/libvcl641ss.so #32 0xfebe3d64 in __1cLApplicationHExecute6F_v_ () from /tools/openoffice/1.0.3/program/libvcl641ss.so #33 0x223e0 in __1cHDesktopEMain6M_v_ () #34 0xfebe6e38 in __1cGSVMain6F_C_ () from /tools/openoffice/1.0.3/program/libvcl641ss.so #35 0x37c08 in main ()
JA->AMA: OD remembered a bugfix for 0001.1 where he changed something at the timer function. Probably this fix needs to get as a patch into a ooo1.0.4. Otherwise this doesn't seem to be reproducible, unfortunately...
OD->AMA, JA (23.05.2003): Trying to reproduce under Solaris. Test case: simple writer document with text only, but more than 1000 thousand pages. Thus, auto saving needs some time. Editing text and new paragraphs with auto saving interrupting the typing. Test results: no crash reproduced. Thus, defect still unconfirmed.
We're not able to reproduce it.
SBA->dnilsson: Thank you for supporting OpenOffice.org. You reported based on version 1.0.3. In the meantime, OpeOffice 1.1 was shipped. The version 1.1 has a crash report feature built in that creates and sends crash reports directly into our database. This is the most efficient way to report crashes. After the developers failed to get the problem with the information you provided, I have no choice but setting this issue to "WORKSFORME" as I can't reproduce it. In case you (or someone else) can make this reproducible, feel free to comment, otherwise I will close it soon. Please upgrade to OOo version 1.1 and use the crash reporter tool in the future. A successfully submitted crash report gives more information to the developers than simply filing an issue that lacks a clear description how to reproduce it. Thank you for your comprehension.
SBA: Closed.