Closed Bug 197415 Opened 21 years ago Closed 21 years ago

crash apparently if x render extension not present on server

Categories

(Core Graveyard :: GFX: Gtk, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 175108

People

(Reporter: bc, Assigned: blizzard)

References

()

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021128
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021128

This page crashes the browser in some cases.  It rendered fine without crashing
when run on X on the console and when exported to another display.  However, it
did crash when Mozilla was exported to Xnest and Xvnc from the same system.

In both of these cases there was a warning that the X extension RENDER is
missing from the display (since they don't support it); my other display did
support RENDER.  I would therefore guess that this could be the reason for the
crash.


Reproducible: Always

Steps to Reproduce:
1. Start Xvnc and vncviewer (or else Xnest).
2. Run mozilla exported to that display.
3. Go to http://www.unipalm.com/.

Actual Results:  
Mozilla crashed before the page was completely drawn.

The error details are "BadValue (integer parameter out of range for operation)"
"Details: serial 9069 error_code 2 request_code 53 minor_code 0"

Expected Results:  
It should not have crashed.

Red Hat Linux 8.0 with XFree86-4.2.0.  VNC version 3.3.3r2.

It crashed in these cases:
Did you compile Mozilla yourself?
No, I downloaded the Red Hat 8 / GTK2 RPMs for i386 from the Mozilla website.
-> GFX:Gtk, because not an xlib build
Assignee: Roland.Mainz → blizzard
Component: GFX: Xlib → GFX: Gtk
QA Contact: timeless → ian
dup

*** This bug has been marked as a duplicate of 175108 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.