Apache OpenOffice (AOO) Bugzilla – Issue 106646
Crash when closing documents
Last modified: 2013-07-30 02:37:42 UTC
id: rmwwf2c since I started using OOo when I close one file it will often close all the files that are open. Usually it restores them but on this occassion it didn't. I discarded an untitled file and it took out another untitled before it had been saved. It also took an established file that I can get back but only with the work before I saved the latest I had done on it. The untitled file had a number of days work that is now lost to me becaue none of the three files were restored. I'm really not happy with that. It looks like you are going the way of MS Word and I will have to find another word processing program.
@leoxman: your last remark - feel free to do it. We don't understand blackmail. Now if you'd like to help fixing this bug and if you can reproduce it, then we'd need an exact description on how to reproduce it. Also tell us which OOo version you were using. @all others: crash report id rmwwf2c has the same stack as other crash reports all together grouped into an internal bug tracker ID 124610. Thus we could consider this issue as duplicate from other crash reports. The problem is that all other reports describe very different situations. Thus we cannot reproduce it and probably not fix it.
BTW: after looking at the 1879 duplicate crash reports, a lot concentrate on "Crash after closing document" in OOo 3.1.0. Might be fixed in current 3.1.1 or 3.2.
You have asked for me to reproduce the fault, how do you suggest I do this when it happens to me out of the blue when I'm doing what I assumed was a legitimate action? I'm using version 3.1.1. Is it possible that it is connected with me using Vista? Regarding your first comment - clearly you don't understand what blackmail is because that wasn't what I was doing. I was making a statement of fact. What choice do I have if you can't fix your system? Having submitted a countless number of reports back to you for the same problem and on an almost daily basis for the last year without any response or change, I think I can be allowed the feeling of (what would have been a less insulting word) FRUSTRATION. I came to you because I was having problems with MS Word. If you are viewing it as blackmail you must have an issue about it, which concerns me more than what was within your snide comment to me. Could it be that you are swamped with problems that you, in your words, "can't fix?"
MRU->MAV: can you see something from the stack? It has an extremely high count, so we should care about this anyway... The internal task is closed as duplicate to an issue which is resolved as fixed in 2.0.2... but the reports are based on 3.1.1. Referring to the users, this is not Writer specific and it mainly happens when documents are closed.
mav->sb: The crash happens in configmgr, it seems to be your sourcecode currently. Could you please take a look. The framework implementation in framework::AutoRecovery::implts_flushConfigItem() catches com.sun.star.uno.Exception.
Created attachment 65982 [details] Attaching the crash report info to issue.
With reference to the following, was this to me or was it internal to another OOo engineer? If it was to me I do not have the understanding or ability to do what you are suggesting. mav->sb: The crash happens in configmgr, it seems to be your sourcecode currently. Could you please take a look.
further to my previous comment, if you are suggesting that the problem lies in my computer that would not surprise me. It is a Toshiba P205-S6267, which I think was developed on another planet because it is too complicated for my little brain.
@leoxman: we are analyzing the problem between us. Thanx for having reported. We will ask you if we need further information. @SB: Please take over. Setting as "CONFIRMED" though not reproducible but due to the several crash reports mentioned above.
There is a number of crash reports (archived Sun-internally) for the current configmgr code that we were not able to fix. That is one of the reasons why the configmgr code is currently being re-written completely from scratch, which will hopefully stop those problems. The re-write is tracked at <http://wiki.services.openoffice.org/wiki/Performance/Configuration#Work_in_Progress> and in issue 101955, and it will probably be integrated into OOo 3.3. @leoxman: I plan to make available some sort of snapshot build of that re-write in the near future. As you write that you are experiencing this specific issue rather regularly, it would be great if you could try that snapshot for a little while, to find out whether it will really solve your problem. I will inform you in this issue about the availability of that snapshot, and keep this issue open until then.
Thanks SB I look forward to you notifying me of the snapshot.
@leoxman: Snapshot builds of the CWS (based on DEV300m66) are now available, see <http://blogs.sun.com/GullFOSS/entry/a_new_configuration>. (As noted there, do make sure to backup your existing OOo user installation, so you can painlessly switch back from the snapshot to your previous OOo installation.)
Created attachment 67108 [details] OO Writer 3.1.1 crashes (and closes all windows) on Windows XP when I close this file (it is read-only). When is it going to be fixed?
q0k: The attached 3sem-program-electricity_and_magnetism.doc produces a crash that is unrelated to this issue, and the corresponding issue has apparently already been fixed in the latest OOO320_m9 OOo 3.2 release candidate.
@leoxman: CWS sb111 is now integrated into DEV300_m74, towards OOo 3.3. You can currently download Developer Snapshot builds of the DEV300_m74 (or later) milestone at <http://download.openoffice.org/next/index.html>.
thanks sb I have downloaded the version 3.3 and will monitor its performs and get back to you if I have anymore problems.
Reset assignee on issues not touched by assignee in more than 1000 days.