Closed
Bug 69204
Opened 25 years ago
Closed 25 years ago
Mozilla 0.8 crash (GDK error)
Categories
(Core :: Internationalization, defect)
Tracking
()
People
(Reporter: ktoman, Assigned: bstell)
References
()
Details
(Keywords: crash)
Looking on http://www.debian.org crashes mozilla0.8 (repeatable). I use
Debian/Woody (testing) distribution (glibc-2.2.1, gtk 1.2.8 (helix2), gdk-imlib1
1.9.8.1 (helix6), libgdk-pixbuf2 0.9.0 (helix8)). The following code (isolated
from debian.org website) crashes moz.:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
<HEAD></HEAD>
<BODY>
한국어 <-- without this line it works as expected -->
</BODY>
</HTML>
The mozilla's output is:
Gdk-ERROR **: BadAlloc (insufficient resources for operation) serial 4050
error_code 11 request_code 45 minor_code 0
Comment 2•25 years ago
|
||
blizzard and pavlov- this is a problem causee by an exit inside GTK. what should
we do with this.
Also, see similar issue in 69204
I think that is a different bug but it exit by the same code.
| Assignee | ||
Comment 4•25 years ago
|
||
is this the same problem as bug 59355 ?
http://bugzilla.mozilla.org/show_bug.cgi?id=59355
| Assignee | ||
Comment 5•25 years ago
|
||
This error appears to come from gdk.c line 1054:
static int
gdk_x_error (Display *display,
XErrorEvent *error)
{
if (error->error_code)
{
if (gdk_error_warnings)
{
char buf[64];
XGetErrorText (display, error->error_code, buf, 63);
#ifdef G_ENABLE_DEBUG
g_error ("%s\n serial %ld error_code %d request_code %d minor_code
%d\n",
buf,
error->serial,
error->error_code,
error->request_code,
error->minor_code);
#else /* !G_ENABLE_DEBUG */
fprintf (stderr, "Gdk-ERROR **: %s\n serial %ld error_code %d
request_code %d minor_code %d\n",
buf,
error->serial,
error->error_code,
error->request_code,
error->minor_code);
exit(1);
#endif /* G_ENABLE_DEBUG */
}
gdk_error_code = error->error_code;
}
return 0;
}
| Assignee | ||
Comment 6•25 years ago
|
||
I believe that this bug is a dup of bug 59355
http://bugzilla.mozilla.org/show_bug.cgi?id=59355
*** This bug has been marked as a duplicate of 59355 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•