Bug 463137

I also tested 3.0.0beta5 and 3.0.1-1, also crash and logout system.

Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

First of all, could we get output of the command

	rpm -qa *xulrun* *firefox* *mozilla* *flash* *plugin*

Please also install firefox-debuginfo (debuginfo-install is from
yum-utils package).

	debuginfo-install firefox

Then run firefox with a parameter -g. That will start firefox running inside of gdb debugger. Then use command run and do whatever you did to make firefox crash. When it happens, you should go back to the gdb and run

	(gdb) thread apply all backtrace

This produces usually many screens of the text. Copy all of them into a text editor and attach the file to the bug as an uncompressed attachment.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

(In reply to comment #2)
> Thanks for the bug report.  We have reviewed the information you have provided
> above, and there is some additional information we require that will be helpful
> in our diagnosis of this issue.
> 
> First of all, could we get output of the command
> 
>  rpm -qa *xulrun* *firefox* *mozilla* *flash* *plugin*
> 
> Please also install firefox-debuginfo (debuginfo-install is from
> yum-utils package).
> 
>  debuginfo-install firefox
> 
> Then run firefox with a parameter -g. That will start firefox running inside of
> gdb debugger. Then use command run and do whatever you did to make firefox
> crash. When it happens, you should go back to the gdb and run
> 
>  (gdb) thread apply all backtrace
> 
> This produces usually many screens of the text. Copy all of them into a text
> editor and attach the file to the bug as an uncompressed attachment.
> 
> We will review this issue again once you've had a chance to attach this
> information.
> 
> Thanks in advance.

Hi Matej,Since firefox will not only crash and it will logout the X system, how could i get the backtrace?

so, when you are trying that running of firefox in gdb (you can redirect its stdout and stderr to the logfile for an additional security) there are no messages anywhere? I mean, when you try

gdb /usr/bin/firefox 2>&1 |tee firefox-log.txt

(and then you do what described above), the file firefox-log.txt is empty?

The log is not empty but it will still cannot catch the backtrace.Following is the content of log:

------------------------
GNU gdb Red Hat Linux (6.3.0.0-1.159.el4rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...Using host libthread_db library "/lib/tls/libthread_db.so.1".

(gdb) r
Starting program: /usr/lib/firefox-3.0.2/firefox-bin 
[Thread debugging using libthread_db enabled]
[New Thread -1208248640 (LWP 26164)]
[New Thread -1214252128 (LWP 26167)]
[New Thread -1227883616 (LWP 26168)]
[New Thread -1240466528 (LWP 26169)]
[Thread -1240466528 (LWP 26169) exited]
[New Thread -1250956384 (LWP 26170)]
[Thread -1250956384 (LWP 26170) exited]
[New Thread -1250956384 (LWP 26171)]
[New Thread -1240466528 (LWP 26172)]
[New Thread -1263535200 (LWP 26173)]
[New Thread -1285555296 (LWP 26174)]
[New Thread -1296045152 (LWP 26175)]
[Thread -1285555296 (LWP 26174) exited]
[New Thread -1285555296 (LWP 26176)]
Gecko: Fatal IO error 104 (Connection reset by peer) on X server :0.0. 
------------------------------------------------------------

Moreover,when i login via vnc(both from my laptop and from the debugging machine) and launch firefox to open that URL, it will NOT crash and X server will not down. And, when i open the URL with opera on debugging machine,it will not crash or down the X server also.

Please attach your X server config file (/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.

Could you please also try to run without any /etc/X11/xorg.conf whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Actually, this is duplicate for RHEL4 of bug 455359

Created attachment 317643 [details]
xorg.conf

The debugging machine is using nvidia video card, and system is using nvidia driver also.

#lspci |grep VGA
06:00.0 VGA compatible controller: nVidia Corporation NV41 [GeForce 6800 GS] (rev a2)


xorg.conf
...
Section "Device"
        Identifier  "Videocard0"
        Driver      "nv"
        VendorName  "Videocard vendor"
        BoardName   "NVIDIA Unknown (generic)"
EndSection
...

Created attachment 317644 [details]
Xorg.0.log

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

1603766 build (dist-4E-qu-candidate, /cvs/dist:rpms/xorg-x11/RHEL-4:xorg-x11-6_8_2-1_EL_54) completed successfully

MODIFIED

I tested with with following configuration:
firefox-3.0.5-1.el5_2 
three resolutions [800x600, 1024x768, 1152x864]
Intel 910GL Integrated Graphics Controller

[PASSED] [RHEL5.3-Client-20090106.0] - Fresh installed OS

(Firefox works fine)
Thanks

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-0998.html