Issue 2563 - unrecoverable error
Summary: unrecoverable error
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: 641
Hardware: PC Windows 98
: P4 Trivial (vote)
Target Milestone: ---
Assignee: stefan.baltzer
QA Contact: issues@sw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-12-17 14:34 UTC by simonbr
Modified: 2003-09-08 16:56 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description simonbr 2001-12-17 14:34:20 UTC 
Hi, 
I got two unrecoverable errors within an hour when typing a document. The 
information I can give you is probably not enough to go on, but you never know.

The document is straightforward: <2 page, font=thorndale 12, some bullets, some 
bold, some italic; nothing exotic.
During typing, the document was autosaved, the "unrecoverable error" dialog 
came up, the Writer window closed, OOo splash screen came up, the file could be 
reloaded, and no editing changes were lost. 

I have autosave disabled, so I suppose the autosave occurred as a response to 
the unrecoverable error.
I had auto-spell checking enabled, but (other than normally) most of this text 
was Dutch, so there were a lot of crinkly red lines.
Both times I may have typed a few words after a period of inactivity.
The document was "untitled" and had not been saved under it's own name yet.
Some time after this had happened twice, I noticed 3 butterfly icons in the 
system tray when the taskbar popped up (it has "auto hide" enabled) but moments 
later two of them had disappeared again.

BTW, is there a way to find out more details when an unrecoverable error 
occurs? A log file or something? It would be helpful in a situation like this. 

Best regards, 
Simon.
Comment 1 stefan.baltzer 2002-01-15 11:34:29 UTC 
The best is always to make it reproducible for us because we have debug environments on several 
platforms. This enables us to find out what went wrong, if it still occurs in a current version, 
and, of course, the developer may check his attempts to fix it "on the fly".

I am not a developer myself, but at least a "Dr.Watson" log file is nothing but a prrof for us 
that a crash really occured. You may browse the developer boards/mailing lists to find out 
what's meaningful, but from my point of view it's ALWAYS best to make it reproducible for others 
by giving a precise description of you system and what exactly to do to (step-by-step so that my 
grandma could reproduce it)

Please attach the document and reassign the issue to me. Thank you.
Comment 2 simonbr 2002-01-26 19:50:11 UTC 
Hi Stefan, 
Atually I don't know anymore which document I was working on. I also 
think this is the kind of problem that is very difficult to 
reproduce. So if my initial description did not ring any bells, I 
propose to resolve the issue as "not reproducible", and hope that 
whatever may have caused this error will be fixed in the ongoing 
development.
Comment 3 stefan.baltzer 2002-03-04 17:59:08 UTC 
Yes, this seems to be the best thing in this case.
Comment 4 stefan.baltzer 2002-03-04 17:59:32 UTC 
Closed.