motrei Reporter
	Description • 24 years ago

Click on http://www.electronicnews.com . The browser crashes. I have tried this
with the April 19 and April 18 nightly builds
mozilla-gcc295-i686-pc-linux-gnu.tar.gz .

This crash must be recent; it doesnt happen with the April 15 nightly build.

I am running Mandrake Linux 7.2 (2.2.17-21mdk kernel, glibc 2.1.3) on an
AMD Athlon 700 with 256M RAM. I am running XFree86 4.0.1 with an Nvidia
GeForce2MX card using the Nvidia drivers. 

This site requires a Java plugin. It seems the window requesting the plugin
comes up and then the browser crashes.FYI, I dont have any plugins installed.

When it crashes, it gives the following output:

[akumar@rastaman mozilla-gcc295]$ ./run-mozilla.sh ./mozilla-bin
MOZILLA_FIVE_HOME=/ajay_local/mozilla/night19apr2001/mozilla-gcc295
  LD_LIBRARY_PATH=/ajay_local/mozilla/night19apr2001/mozilla-gcc295
    
LIBRARY_PATH=/ajay_local/mozilla/night19apr2001/mozilla-gcc295:/ajay_local/mozilla/night19apr2001/mozilla-gcc295/components
       SHLIB_PATH=/ajay_local/mozilla/night19apr2001/mozilla-gcc295
          LIBPATH=/ajay_local/mozilla/night19apr2001/mozilla-gcc295
       ADDON_PATH=/ajay_local/mozilla/night19apr2001/mozilla-gcc295
      MOZ_PROGRAM=./mozilla-bin
      MOZ_TOOLKIT=
        moz_debug=0
     moz_debugger=
Registering plugin 0 for: "*","All types",".*"
Gdk-ERROR **: BadDrawable (invalid Pixmap or Window parameter)
  serial 17 error_code 9 request_code 55 minor_code 0

	Asa Dotzler [:asa] Assignee
	Comment 1 • 24 years ago

related to bug 76713 maybe?

	Matthew Cline
	Comment 2 • 24 years ago

Works for me on Linux build 2001041908, Linux 2.4.3-ac3 i686, RedHat6.1,
XFree86 4.0.2

	Keyser Sose
	Comment 3 • 24 years ago

Reporter do you have the stacktrace from the crash?

	motrei Reporter
	Comment 4 • 24 years ago

The crash did not produce a stack trace, so I dont have one. However, the build
id of the build I was using is: 2001041909, which is 1 rev later than the one 
Matthew Cline tried.

	motrei Reporter
	Comment 5 • 24 years ago

I now also have this crash on my home machine : an Intel Pentium 3 933MHz 
with 256M RAM running Mandrake Linux 7.2 with Xfree86 4.0.1. In both cases
I was running icewm at 1600x1200 at color depth 24.

Also, if it helps, here are the rpms related to gdk that I found on my
Mandrake Linux 7.2 system:

gdk-pixbuf-loaders-0.9.0-2mdk
gdk-pixbuf-0.9.0-2mdk
gdk-pixbuf-devel-0.9.0-2mdk

gtk+-1.2.8-6mdk
pygtk-0.6.6-4mdk
gtk+mdk-0.1.3-6mdk
rep-gtk-0.13a-6mdk
gtk+-devel-1.2.8-6mdk
gtkdialogs-1.0-1mdk
gtkglarea-1.2.2-3mdk
gtkmm-1.2.2-3mdk

	motrei Reporter
	Comment 6 • 24 years ago

I can also make it crash in exactly the same way with exactly the same build by
going to http://www.hardocp.com:


Gdk-ERROR **: BadDrawable (invalid Pixmap or Window parameter)
  serial 17 error_code 9 request_code 55 minor_code 0

Note that one thing that is common to both these sites is that a popup seems to
come up for an instant and then the browser crashes. I have visited hardocp.com
before: the popup asks to download/install the flash plugin. As previously 
mentioned, www.electronicnews.com causes a popup that asks to install java. 
Perhaps the problem is related to popup windows?

	motrei Reporter
	Comment 7 • 24 years ago

I figured out how to get a stack trace (attached with gdb before causing the
crash). 

Below is the stack trace I got with www.electronicnews.com. The trace from
hardocp.com is identical. 

Note that this same setup works with previous nightly builds. Did something
recently change in the area of threading, especially between build id 2001041908
and 2001041909? 

Also, once in the debugger, after the crash, if I say cont, the program 
exits with code 01.

(gdb) cont
Continuing.
Gdk-ERROR **: BadDrawable (invalid Pixmap or Window parameter)
  serial 17 error_code 9 request_code 55 minor_code 0

Program received signal SIG32, Real-time event 32.
0x401f417e in sigsuspend () from /lib/libc.so.6
(gdb) where
#0  0x401f417e in sigsuspend () from /lib/libc.so.6
#1  0x401c61a0 in pthread_setconcurrency () from /lib/libpthread.so.0
#2  0x401c627c in pthread_setconcurrency () from /lib/libpthread.so.0
#3  0x401f67b3 in exit () from /lib/libc.so.6
#4  0x406ba4ca in gdk_send_xevent () from /usr/lib/libgdk-1.2.so.0
#5  0x4074fa19 in _XEventsQueued () from /usr/X11R6/lib/libX11.so.6
#6  0x407437ca in XEventsQueued () from /usr/X11R6/lib/libX11.so.6
#7  0x40e7b08d in XtAppPending () from /usr/X11R6/lib/libXt.so.6
#8  0x4081e7ae in _init ()
   from /home/ajay/moz/night19apr2001/mozilla-gcc295/libgtkxtbin.so
#9  0x406f7c27 in g_source_remove_by_funcs_user_data ()
   from /usr/lib/libglib-1.2.so.0

	Doron Rosenberg (IBM)
	Comment 8 • 24 years ago

dupe of 40931

*** This bug has been marked as a duplicate of 40931 ***

	motrei Reporter
	Comment 9 • 24 years ago

If this was closed because it is believed to show up only in low-memory
situations, I want to point out that when I saw the crashes I was nowhere
close to running out of physical memory, let alone swap. This bug seems 
to be closer to bug 76505.

	Fabian Guisset
	Comment 10 • 24 years ago

reopening to dup to the right bug

	Fabian Guisset
	Comment 11 • 24 years ago

correct dup

*** This bug has been marked as a duplicate of 76505 ***