Closed Bug 151674 Opened 22 years ago Closed 22 years ago

X Error (opcode = X_PutImage) -> crash

Categories

(Core :: Graphics: ImageLib, defect)

Sun
Solaris
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: dgp, Assigned: pavlov)

References

()

Details

(Keywords: crash)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.0) Gecko/20020609 BuildID: 0000000000 Reproducible: Always Steps to Reproduce: 1. Start Mozilla. 2. Enter URL in navigation toolbar. Actual Results: When attempting to load the page, Mozilla crashes and the following message is printed to my enclosing shell: X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 72 (X_PutImage) Serial number of failed request: 65 Current serial number in output stream: 85 Expected Results: Page should render, and browsing should continue. I built Mozilla from source. During Mozilla startup, I see these messages in the console: Gdk-WARNING **: shmat failed! Gdk-WARNING **: shmat failed!
Should have also mentioned that I built from the mozilla-source-1.0.tar.gz distribution.
does this problem still exist with 1.1beta?
I cannot reproduce the problem with Mozilla 1.1b. Then I went back and I can no longer reproduce the problem with 1.0 either. So, best mark this one as non-reproducible. Only thing I can guess is that the real bug may have been in the X server, and maybe the sysadmins fixed that.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
I went back to Moz 1.0, and the X error is back. the securityfocus URL below just crash Moz 1.0 on me, just like before.
Back to 1.1b again, and this problem does not appear. There are lots of annoying little problems with 1.1b, so I wish I could go back to 1.0, but I guess I'll stick with the one that doesn't crash on me. (Though I didn't really want to become a beta tester on yet another project.) I leave it up to you whether that means this issue is resolved.
*** Bug 157424 has been marked as a duplicate of this bug. ***
Marking WFM as per reporter comments. No stack. However, if you still crash with 1.0.1 and have a stack, please attach it here and reopen.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago22 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.