Closed
Bug 37917
Opened 25 years ago
Closed 25 years ago
Crash with Gdk-ERROR **: BadMatch on named website
Categories
(Core :: XUL, defect, P3)
Tracking
()
People
(Reporter: cks+mozilla, Assigned: scc-obsolete)
References
()
Details
(Keywords: crash)
Build ID: current CVS tip, recent CVS pull
When I browse http://www.konqueror.org/, the browser dies in the
process of rendering the page (or perhaps in the final stages of
it) with a Gdk-ERROR:
Gdk-ERROR **: BadMatch (invalid parameter attributes)
serial 2109 error_code 8 request_code 73 minor_code 0
Sometimes I will get a SEGV and a crash, sometimes it just exits
afterwards.
crashes older nightlies as well - just tested 2000-042809 linux M16
This is the error output from 2000-042809:
Document http://www.konqueror.org/ loaded successfully
Gdk-ERROR **: BadMatch (invalid parameter attributes)
serial 48686 error_code 8 request_code 73 minor_code 0
Oh no! ./mozilla-bin just dumped a core file.
Do you want to debug this ? You need a lot of memory for this, so watch out ?
[y/n]
older and older: It crashes M16 linux 2000-042416 as well:
Document http://www.konqueror.org/ loaded successfully
Gdk-ERROR **: BadMatch (invalid parameter attributes)
serial 59770 error_code 8 request_code 73 minor_code 0
More or less same backtrace in nightlies 2000-042809 and 2000-042416:
Program received signal SIGSEGV, Segmentation fault.
0x400dea83 in nsStr::Truncate ()
(gdb) bt
#0 0x400dea83 in nsStr::Truncate ()
#1 0x400e2d78 in nsString::AssignWithConversion ()
Comment 5•25 years ago
|
||
This loads fine for me using verification build from this morning. reassigning
to scc to consider possible string problem.
Assignee: trudelle → scc
afranke@ is right..same error messages, crash and backtrace
marking dup
*** This bug has been marked as a duplicate of 37212 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Comment 9•24 years ago
|
||
The bug this is a dupe of has been marked FIXED, and this now WFM under Linux
build 2000102421. Verified dupe.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•