Apache OpenOffice (AOO) Bugzilla – Issue 17168
Crash on recovering aborted save on XL file.
Last modified: 2003-09-08 16:55:29 UTC
Hi, Whilst working on an Excel file containing several sheets of mainly text entries, a save operation cause OOo to freeze in X (X io error). I had to kill OOo to free up the screen. When I relaunched OOo, it asked me if I wanted to recover the file. OOo promptly aborted. The crash report is here : sh: -c: line 1: syntax error near unexpected token `(' sh: -c: line 1: `crash_report -p 8353 -s 11 -xml (null) -stack (null)' Fatal exception: Signal 11 Stack: /usr/local/OpenOffice.org1.1rc1_athlon/program/libsal.so.3[0x40ba4b63] /usr/local/OpenOffice.org1.1rc1_athlon/program/libsal.so.3[0x40ba4cee] /usr/local/OpenOffice.org1.1rc1_athlon/program/libsal.so.3[0x40ba4db9] /lib/i686/libpthread.so.0[0x411185ce] /lib/i686/libc.so.6[0x4132e3b8] /usr/local/OpenOffice.org1.1rc1_athlon/program/soffice.bin(_ZN7desktop7Desktop9E xceptionEt+0x7a)[0x8063024] /usr/local/OpenOffice.org1.1rc1_athlon/program/libvcl645li.so(_ZN23ImplVCLExcept ionHandler6signalEP13oslSignalInfo+0xb3)[0x400e6ed3] /usr/local/OpenOffice.org1.1rc1_athlon/program/libvos3gcc3.so(_ZN3vos28_cpp_OSig nalHandler_FunctionEPvP13oslSignalInfo+0x18)[0x40b0c574] /usr/local/OpenOffice.org1.1rc1_athlon/program/libvos3gcc3.so(_Z24_OSignalHandle r_FunctionPvP13oslSignalInfo+0x26)[0x40b0c556] /usr/local/OpenOffice.org1.1rc1_athlon/program/libsal.so.3[0x40ba4c0b] /usr/local/OpenOffice.org1.1rc1_athlon/program/libsal.so.3[0x40ba4d9a] /lib/i686/libpthread.so.0[0x411185ce] /lib/i686/libc.so.6[0x4132e3b8] /usr/local/OpenOffice.org1.1rc1_athlon/program/libcppu.so.3(uno_type_any_assign+ 0x2f)[0x40b6f9e7] /usr/local/OpenOffice.org1.1rc1_athlon/program/soffice.bin(_ZN7desktop7Desktop11 OpenClientsEv+0x9f9)[0x80667a5] /usr/local/OpenOffice.org1.1rc1_athlon/program/soffice.bin(_ZN7desktop7Desktop16 OpenClients_ImplEPv+0x11)[0x80659c3] /usr/local/OpenOffice.org1.1rc1_athlon/program/soffice.bin(_ZN7desktop7Desktop24 LinkStubOpenClients_ImplEPvS1_+0x18)[0x80659b0] /usr/local/OpenOffice.org1.1rc1_athlon/program/libvcl645li.so[0x40223830] /usr/local/OpenOffice.org1.1rc1_athlon/program/libvcl645li.so(_Z19ImplWindowFram eProcPvP8SalFrametPKv+0x441)[0x40224025] /usr/local/OpenOffice.org1.1rc1_athlon/program/libvcl645li.so(_ZN12SalFrameData1 9HandleClientMessageEP19XClientMessageEvent+0xb3)[0x4028348f] /usr/local/OpenOffice.org1.1rc1_athlon/program/libvcl645li.so(_ZN12SalFrameData8 DispatchEP7_XEvent+0x4f4)[0x40283ed8] /usr/local/OpenOffice.org1.1rc1_athlon/program/libvcl645li.so(_ZN10SalDisplay8Di spatchEP7_XEvent+0x287)[0x402af5f3] /usr/local/OpenOffice.org1.1rc1_athlon/program/libvcl645li.so(_ZN10SalDisplay5Yi eldEh+0xf1)[0x402af349] /usr/local/OpenOffice.org1.1rc1_athlon/program/libvcl645li.so[0x402ab32d] /usr/local/OpenOffice.org1.1rc1_athlon/program/libvcl645li.so(_ZN7SalXLib5YieldE h+0x398)[0x402a9e94] /usr/local/OpenOffice.org1.1rc1_athlon/program/libvcl645li.so(_ZN11SalInstance5Y ieldEh+0x34)[0x402b2c4c] /usr/local/OpenOffice.org1.1rc1_athlon/program/libvcl645li.so(_ZN11Application5Y ieldEv+0x59)[0x400e1ff7] /usr/local/OpenOffice.org1.1rc1_athlon/program/libvcl645li.so(_ZN11Application7E xecuteEv+0x35)[0x400e1f25] /usr/local/OpenOffice.org1.1rc1_athlon/program/soffice.bin(_ZN7desktop7Desktop4M ainEv+0x1a8e)[0x8064f3c] /usr/local/OpenOffice.org1.1rc1_athlon/program/libvcl645li.so(_Z6SVMainv+0x4b)[0 x400e6f41] /usr/local/OpenOffice.org1.1rc1_athlon/program/libvcl645li.so(main+0x1c)[0x402a8 860] /lib/i686/libc.so.6(__libc_start_main+0xc7)[0x4131b7f7] /usr/local/OpenOffice.org1.1rc1_athlon/program/soffice.bin(_ZN6Window11RequestHe lpERK9HelpEvent+0x35)[0x805e431] [1]- Done ./OpenOffice.org1.1rc1_athlon/soffice [2]+ Aborted (core dumped) ./OpenOffice.org1.1rc1_athlon/soffic
I have now tried the same maneuver three times in a row and each time OOo dumps core. Alex
Hi Alex, could you please attach the original file which causes the crash ? Without such a fuile we are not able to reproduce the problem you've described. Best regards Frank
Hi Frank, Unfortunately for everyone concerned, that is impossible. I am an attorney and the file in question relates to attorney privileged information. So it looks like we're stuck. Alex
Hi Alex, is it possible, that you change the content to let's say XXX using Excel ? Maybe you can find such an installation and then check again in OOo that the file still crashes and attach this Excel file to this Issue ? Thanks for your help. I assign this one to Peter, as he thinks he had seen the stack sometimes ago. Frank
Well since I have been Microsoft free for nearly 10 years now, I don't think that is going to be possible. I've never ever actually had a copy of Excel installed on any of the machines I've ever worked with. What I can tell you is that the file was initially produced on a Mac OS9 version of Microsoft Office (although which version precisely I do not know), so maybe that has something to do with it. I had carried out some changes with respect to font type and font size before OOo froze on me, thereby obliging me to kill it. The problem seems to lie in the fact that the backup copy created when OOo goes belly up gets corrupted in some way, and that this is what causes the core dumps when you try to reload from "recover saved file" dialog. The reason I say this, is that when I said no to the dialog, OOo starts as normal with the document-less window. If I then load my original file (and not the one that OOo allegedly backed up), the file loads fine, so the issue really is with the temporary copy that is created when OOo dies. Alex
I agree. I just made the mistake of trying to print a spreadsheet without defining a print range. I suspect it was trying to format the entire spreadsheet for printing. After five minutes, I killed it. When I restarted, it asked if I wanted to reload the spreadsheet. Since I had not saved it, I clicked on "Yes" at which point OOo crashed. I then reopened and clicked on "No" and everything went fine. In my case, I would assume a corrupted file or a tag to try to continue printing the spreadsheet was not removed (why should it with a hard kill?). Perhaps a warning could be included that would read: "Opening a corrupted file could cause the program to crash." That way at least you'd be warned.
Hi, no idea what's going on. @Niklas: Are you able to get some information from the stack? If not I'm afraid you have to close it as invalid. Best regards, Peter
Without the file that crashes during save, I can't do much either.
Closing - please reopen if you can attach a file that shows the problems at saving.