Apache OpenOffice (AOO) Bugzilla – Issue 27492
Font engine corruption and incompatibility with Delphi
Last modified: 2004-04-08 14:59:09 UTC
If I have Impress or Writer running for a while, frequently it will become unable to use the correct font. Instead, it uses some kind of system font (I suspect) and thus everything looks odd. In fact, sometimes it makes other running applications (eg, Mozilla) unable to get their fonts too. So it seems to corrupt the font engine in Windows. This issue can be triggered easily by running Delphi (I use Delphi 7 enterprise) and OOo at the same time. OOo can easily trigger errors like "Incorrect parameter" or "Unable to draw" when I switch to Delphi. With Delphi's presence, OOo can also easily crash, particularly when I insert a graphic (by pasting). Before it dies, it will always display the document's text in a special font first, followed by a system message box saying something like "Application has caused an unrecoverable error". I am using the Chinese version (big5) of Win98 second edition. I am using the Unicode layer installed by OOo's setup program.
cp->freemant: please try the 1.1.1, please send an error report (stack trace) when the office crashes. cp->sba: this may or may not have something to do with internal #112304#. However I have no chance to test this. Can you test on Win98 Chin ? or push this to China ?
Thanks for the reply. I'll try 1.1.1. Regarding the stack track, how to generate it?
Just tried 1.1.1. It is still the same. I can crash it in a few trials (with Delphi opened). When it dies, it displays a error report window. Is clicking the "error report" button supposed to show the stack trace? I tried but it opens a window with nothing in it (no text).
Wait. After rebooting the computer, it seems that 1.1.1 is working without this problem. I'll continue to test it. Thanks!
yep, please try to send the error report, press "Enter" key several times if it is empty. At least I hope that it works
It happens again even with OOo 1.1.1. Please find the stack trace attached.
Created attachment 14402 [details] Stack trace when inserting a graphics into Writer (while Delphi is open)
Created attachment 14403 [details] Crash again when resizing a graphics
Created attachment 14404 [details] Crash again when resizing a graphics to its original size
I had a look at the stacktrace and could see that OOo was unable to create a window. Because the description mentions font problems too and the system is Windows98, it seems that the system resources are exhausted, either due to OOo or due to any other process that is running simultaneously. So I woud suggest tracking down which process causes those problems using a resource meter. You can for example download such a tool from http://www.techadvice.com/w98/R/Resource_Meter.htm and check if the resources are going dramatically down during the use of OOo. It would especially be useful to see if all resources reach the level they had before starting OOo after you close it. Then do the same with delphi. If both applications behave well, it may be that the sum of both applications together consumes too much resources, in which case you would have to restrict yourself to only one of them at a time...
Thanks for the tip. Experiements: 1. Neither OOo nor Delphi is open. System (and GDI) resources: 70% free. 2. OOo is open alone. System (and GDI) resources: 63% free. 3. OOo is open and a complex document containg graphics is loaded. System (and GDI) resources: 63% free (yes, no change at all). 4. Insert a new graphics (screenshot) into an empty document. System (and GDI) resources: 31% free. Why this significant change? Quitting OOo restores to 70% free. Inserting another graphics do NOT change the resources used. 5. Delphi is open alone. System (and GDI) resources: 45% free. 6. OOo (empty doc) and Delphi are both open. System (and GDI) resources: 39% free. It is obvious that if now I insert a graphics, about 32% will be gone. This would leave only 7% free. That's why the apps can crash easily at this state. So, I guess the question is why the first insertion of a graphics takes so much resources?
The resource problem is fixed with Issue 21114. The fix will be in OOo2.0 and is already available in the developer builds (which of course still have pre-alpha status, so actually using them is not recommended). *** This issue has been marked as a duplicate of 21114 ***
closing