To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=95974
                 Issue #|95974
                 Summary|Crash after some time of opening a large document (odt
                        |)
               Component|Word processor
                 Version|OOo 3.0
                Platform|Unknown
                     URL|
              OS/Version|Windows XP
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|ui
             Assigned to|writerneedsconfirm
             Reported by|raindrops





------- Additional comments from [EMAIL PROTECTED] Fri Nov  7 18:06:16 +0000 
2008 -------
Writer 3.0 crashes a few seconds after loading a large odt (375+ pages) 
document. 

The previous RC version did not crash. 

Once the document is loaded, the CPU quickly climbs to 100% and stays there.

I know that Ooo has some problematic code for aligning the contents of large
complex documents (it enters endless loops which can't be exited). So I used the
"Tools> Update>Update All" menu. Writer completes this successfully. However,
within a few seconds after that, it crashes.

When Writer crashes, it simply vanishes, and the recovery wizard starts. 

I can send the problematic document if you could provide an email address.

Thanks.

---------------------------------------------------------------------
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