To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=64353
------- Additional comments from [EMAIL PROTECTED] Tue Apr 18 07:27:17 -0700 2006 ------- Sorry for the delay in getting back on this. Also, sorry can't send out the offending files since they are company internal data. The 100% cpu state of soffice.exe happened after the files were open for several days (but not really editing, just read-only). Tried again today to duplicate the problem but couldn't exactly duplicate in a short time. However, did notice that when I did a print preview with the 2 large files open, ooO writer locked up and soffice.exe was at near 100% and had to kill ooO writer. However, soffice.exe went back to zero after killing the writer tasks. So similar but not exactly the same. --------------------------------------------------------------------- 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]
