To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=69123
                 Issue #|69123
                 Summary|OOo crash with HotSpot detected
               Component|framework
                 Version|OOo 2.0.3
                Platform|PC
                     URL|
              OS/Version|Linux
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|code
             Assigned to|tm
             Reported by|alfonsname





------- Additional comments from [EMAIL PROTECTED] Wed Aug 30 15:44:04 -0700 
2006 -------
Hi,

I've got OOo 2.0.3 german (rpm) running on an FC5 x86 host.
I'm editing a odb Databasedocument mit HSQLDB at about 5 MB.
Sometimes OOo just crashes, I could not find out why. It mostly happens when
editing macro code, but also when editing formular documents or dialog elements.
It also did happen that then some xml files within the odb file got corrupted,
after a Crash. (OOo then tells me "I/O Error in ...xml")

As I fould some hs_err_pid*.log files in my home directory, I thought of
updateing the java engine from sun j2se jdk 1.5.0-06 to 1.5.06-08; but this also
could not fully remove the crashes. 

That's why I'd like to attach such a log file to this bug report, maybe it helps
somebody here.

Sincerly, 
 AZ

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to