Closed
Bug 78108
Opened 24 years ago
Closed 18 years ago
X Error of failed request: BadLength (poly request too large or internal Xlib length error)
Categories
(Core :: XUL, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: timeless, Assigned: timeless)
References
Details
(Keywords: crash)
SunOS 5.7 Generic_106541-15 sun4u sparc SUNW,Ultra-2
xlib cvs build from this morning, using -display to MIX 2.0.3 800x600x24bit
XpmSuccess
X Error of failed request: BadLength (poly request too large or internal Xlib
length error)
Major opcode of failed request: 72 (X_PutImage)
Serial number of failed request: 43851
Current serial number in output stream: 43856
* Pavlov expects that timeless is using xlib again
sorry, i had to try. After I ignored the one major assert, it was actually
usable :)
Comment 1•24 years ago
|
||
reassigning to timeless. xlib toolkit bug. find someone that cares.
Assignee: pavlov → timeless
Component: ImageLib → XP Toolkit/Widgets
Comment 2•23 years ago
|
||
I was just going to open a Phoenix bug about a reproducable crash that I have,
when I searched for the error message I get. Going to
http://jota.sm.luth.se/~anedah-9/misc/george.ogg crashes Phoenix for me
everytime. The server is misconfigured causing it to send a mime-type of
text/... for that file, but nonetheless it shouldn't crash. I have had
confirmation from two other people running Debian GNU/Linux that this crash
occurs. I can only reproduce it in Phoenix, but this other person saw it in
Mozilla also.
The output of the crash is:
Gdk-ERROR **: BadDrawable (invalid Pixmap or Window parameter)
serial 41950 error_code 9 request_code 70 minor_code 0
Gdk-ERROR **: BadLength (poly request too large or internal Xlib length erro
serial 41952 error_code 16 request_code 151 minor_code 0
Let me know if you prefer a new bugreport for this instead. I see this crash on
Linux.
Comment 3•18 years ago
|
||
Xlib port has been removed from trunk (bug 326152)
-> WONTFIX
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•