Apache OpenOffice (AOO) Bugzilla – Issue 8072
X Server Crashes When Loading an MS Word document
Last modified: 2007-11-05 15:46:52 UTC
I tried to load a fairly average MS Word document and it brought down the whole X server. I tried it multiple times to make sure it wasn't a fluke bug. I'm running on the new Red Hat 8.0. The document actually appears to load ok, but as soon as I hit any button or scroll bar the X server crashes. Therefore I'm thinking that this document somehow puts open office into an unstable state. I can email you the document if you're interested in testing with it. The document was created on Windows NT using Office 2000.
Created attachment 3065 [details] This is the file that crashes the server.
It appears you're not alone, I am writing a technical dosument in OO1.0.1, RH7.2. I can work on the document just fine... but... If I try to scroll up/down through the document the X-server crashes and reloads... No errors are written in the /var/logXFree86.x.log files... I thought it had to do with X4.1.0 that I was using. Updated to 4.2.0 but it's still there... Switched between Gnome, Enlightenment and twm but the problem persists. I'll try to generate a core file using the debug option on /etc/X11/XF86config-4 but dont know what to do with it... Anybody can help out there?
Sorry for the post bombing but just got an idea that might help, could this be related to issue #3360 provided some memory related option is changed in the Xserver/kernel?? I do remember that I changed some setting to allow memory consuming programs to run up to the point the kernel had to kill em... But I fail to find the setting again to verify this. Under such a situation would the OO. display the memory shortage dialog? I checked with a "top" and every time a new formula scrolls through, the memory allocation goes way up. The problem is that it doesn't go down!!! I'd really like to help on this so if somebody knows, tell me how to get a trace from the Xserver... George
Thank you for using and supporting OOo. Unable to duplicate on RH 8.0, OOo 643. Will test on OOo 1.0.1 later.
Created attachment 3163 [details] Native OO writer file that crashes the Xserver, Open and then scroll through the document (256MB RAM)
Installed the 643 build and checked it with the sxw. I posted... You have to scroll all the way up/down a couple of times but it's still there.... RH7.2 X4.2.0 Gnome1.4.0.4 256MB RAM
Found a workaround, see if it works for you... Uncomment the SAL_ANTIALIAS_DISABLE in soffice script. I tried this with build 638 and 643 it works for both biulds with the attached OO document. Got the idea from issue #1106. It seems that the xfs server is causing the Xserver to crash. I can attach a detailed setup of my font system if needed.
Just noticed that this only goes wrong for me if I use the scroll weel of my mouse!! If I use the page UP/DN keys everything works... So after all maybe its not the xfs but something else... I'll start a different issue for this sorry to drive everybody crazy... jumped to issue #8505 George
George thanks for the extra comments. We'll be waiting for your new issue. jtsmith, did any of George's comments help you? Unable to duplicate on RH 8.0, RH OOo 1.0.1. Document loads fine and OOo does not crash.
JA->US: Ulf, please check this area again just to make sure it was a freetype problem. Stefan said I might send this issue to you
If an app crashes X, then it's X's fault. X is supposed to be bulletproof.
Pls. try again in OOo 1.1 RC. Should be resolved.
I have recently Updated to X4.2.1, OO1.1 and did some clean up in my fonts. This issue is no longer repeatable. There is a number of reasons why this could happen, I have to agree with Dan though that it IS X's fault if it dies because of a defective appl. There is a possibility that the crash would happen because of a defective font. In my system I added some window fonts and tweaked the default system fonts as well. Anyway, all well that ends well, the bug is gone, antialiasing and everything works fine, no server crashes with 1.1.
Closing Resolved/Invalid issues. If new information/rationale is forthcoming, the issue can be reopened. Tam
*** Issue 79668 has been marked as a duplicate of this issue. ***
oops.
SBA: Not reproducible, set to WORKSFORME.
Closed.