Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Writer crashed during autosave | ||
---|---|---|---|
Product: | Writer | Reporter: | simonbr |
Component: | code | Assignee: | Mathias_Bauer |
Status: | CLOSED FIXED | QA Contact: | issues@sw <issues> |
Severity: | Trivial | ||
Priority: | P3 | CC: | issues |
Version: | 638 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows 98 | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
simonbr
2001-10-10 13:10:02 UTC
1. Does this ALWAYS happen when autosave starts to work? 1.a. (If not): What does it take to make this occur (start from an empty document up to the type of doc where it happened) 2. Is it Text documents only? (Try a spreadsheet with the same path/name/ same objects inside) 3. Was that file saved before? 4.a. (If so): Where was the file stored (complete path)? 4.b. (If not): Where is your "default saving path" (complete path)? 5. Did you enable autosave "with prompt" or without? Please comment. Thank you. > 1. Does this ALWAYS happen when autosave starts to work? No, it was just this once. > 1.a. (If not): What does it take to make this occur (start from an > empty document up to the type of doc where it happened) It was a small document (<1 page) in Writer. I was using the drawing tools. It might have to do with the fact that the autosave prompt received OK (I was just pressing the ENTER key) almost immediately it came up. There is nothing more specific I could put my finger on. > 2. Is it Text documents only? (Try a spreadsheet with the same > path/name/ same objects inside) I doubt if I can even reproduce the error with a text document. > 3. Was that file saved before? I'm not sure. > 4.b. (If not): Where is your "default saving path" (complete path)? I think it is "C:\My Documents". I am not sure if it was at the time this error occurred. > 5. Did you enable autosave "with prompt" or without? With prompt. I don't have the impression this error is likely to occur, so it may be quite difficult to reproduce. This is the reason I included the stack trace in the hope you could use it to find out what happened. I later switched autosaving off because OOo is supposed to have an autorecovery mechanism analogous to that in MS Office, which is what I actually want. I haven't been able to figure out what additional value "autosaving" could actually have? Best regards, Simon. Mathias, If you can't figure out how to reproduce this, I'm afraid we have to leave it as not reproducible and hope that things get better along with the improvement of stability in general. Reassigned. Sorry, but the stacktrace doesn't give a valid information to me mh->mba: I think, that this could be SfxShell::GetSlotState(...). Sorry, the last comment was incomplete because I accidently hit the return key. What I wanted to say: the stacktrace doesn't give a valid information to me, because I examined the function where the crash occured in close detail, and I didn't find any chance for a crash. We made some changes there that made the code a little bit safer, and this happened after the 638 build. There was one code line that could end in a NULL pointer access under some rare conditions. May be you had one?! Anyway, this NULL pointer access will not happen anymore. I couldn't reproduce this bug in any build (638, 641), so I can only assume that my code change hopefully fixed the bug. Seems to be fixed, got no response from submitter. As the error is probably hard to reproduce, it is difficult to determine if if it has actually been fixed. But I fully agree with closing the issue. Thanks! |