Issue 2910 - "An unrecoverable error has occured"
Summary: "An unrecoverable error has occured"
Status: CLOSED FIXED
Alias: None
Product: udk
Classification: Code
Component: code (show other issues)
Version: current
Hardware: All All
: P1 (highest) Trivial (vote)
Target Milestone: ---
Assignee: joergbudi
QA Contact: issues@udk
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-01-22 09:29 UTC by dgrant
Modified: 2004-10-15 04:12 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description dgrant 2002-01-22 09:29:00 UTC
I receive the error message "An unrecoverable error has occurred.  All modified
files have been saved and can probably be recovered at program restart."  This
happens seemingly randomly, but I usally have to do some action for it to
happen.  Today it happened once while hitting the "yes" button when asked if I
wanted to save the document after exiting.  It also happened to me today after I
right-clicked on a frame and tried to change it's properties.

This happens on Linux and also on Windows with 641C.

I just upgraded from 641 and I don't remember getting these with 641, although
it was a long time since I used 641, so I can't remember.
Comment 1 kay.ramme 2002-01-28 10:41:15 UTC
Please specify in more detail what you are doing to crash OO.o.
E.g. openening this and clicking that..

Comment 2 dgrant 2002-01-28 16:36:19 UTC
One example of when this happens:

I right click on a frame's border, and then I left-click on the
"Frame..." option, to edit the frame's properties.  I get the error
message immediately after left-clicking.  This error is very
repeatable.  It is just one example of when the "unrecoverable error
has occured" message appears.  I will add more situations as I notice
them, but I have had them for many different things before.
Comment 3 dgrant 2002-02-04 09:45:57 UTC
It looks like this is a 641c issue, because I just reverted to 638c 
and I don't have any problems so far...

I had this error occur in a document today which was really annoying 
because I could no longer use the document.  I had copy and pasted a 
drawing from the OpenOffice Drawing program.  It was fine, no 
problems.  The next time I opened the document later that day, after 
rebooting the computer, OpenOffice crashed every time I even 
scrolled, and the drawing entered the screen.  There was an arrow on 
the drawing, that came up okay, then I scrolled one more line down, 
to where there was a little text box...then boom!  it crashes.  I did 
this over and over.  Very repeatable.

This is a very far-reaching problem as far as I can see.  It can be 
triggered by various sources.  Like I said, this has happened to me 
in Linux as well as Windows 98SE.

Thanks.
Comment 4 lsuarezpotts 2002-02-07 03:28:11 UTC
Reassigning to UDK, as OI is closed.
Louis
Comment 5 dgrant 2002-02-23 06:01:15 UTC
Assigning this bug to someone else... sorry for passing the buck, but 
I'm not a programmer (at least not a good one) for OpenOffice, I just 
found the bug.  Is this bug obsolete? or duplicate?
Comment 6 kay.ramme 2002-02-28 08:45:34 UTC
Joerg, can you please look for whats getting wrong and dispatch
this issue accordingly?!
Comment 7 joergbudi 2002-02-28 09:47:44 UTC
I can reproduce the frame issue, it happens also when you simly try
Insert/Frame..., so the frame dialog seems to be completely 
inaccessible in OO641C.

It does not occur anymore in one of our later internal builds, so I 
think the bug should be fixed in the next build (probably already in 
the unstable OO642C developer release).


Comment 8 dgrant 2002-02-28 10:00:08 UTC
Somebody speculated (I believe in another related issue) that these 
problems are all due to the fact that gcc 3.x was used for the 641 
build rather than 2.x which was used for 638.  I'm just curious, did 
we revert back to 2.x now?

Also, this crash can be re-created from doing all sorts of things, 
not just frames.  I've caused these crashes on Linux and Windows on 
the same computer.
Comment 9 joergbudi 2002-02-28 10:08:09 UTC
We are still with gcc 3.0. The error arose within some resource 
handling code, so I would not be too surprised, if a similar bug 
strikes you somewhere else.

If you can reproduce them, please post it, so that I can verify, that 
they have also gone.

It is not clear to me, whether the bug occurs because of gcc2->gcc3 
transition or because for some other reason, as I don't know what has 
fixed it.
Comment 10 Martin Hollmichel 2004-10-15 04:12:04 UTC
close issue.