372611 - FF randomly crashes since version 2 - was good up to version 1.5.x

Status: VERIFIED INCOMPLETE

(Firefox :: General, defect)

Description

[Andreas]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686 (x86_64); de-DE; rv:1.8.1.2) Gecko/20070220 Firefox/2.0.0.2
Build Identifier: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de-DE; rv:1.8.1.2) Gecko/20070220 Firefox/2.0.0.2

I get a program exception at least twice daily. That did not happen in 1.5.x trunk, which was a very stable version. What happened in 2.0.x ??? The URL does not matter; sometimes crashes when idle in the background. Other applications do not crash, so it's not a hardware problem.

Reproducible: Didn't try

Steps to Reproduce:
1.
2.
3.

Comment 1

[Ria Klaassen (not reading all bugmail)]

See http://kb.mozillazine.org/Firefox_crashes

Comment 2

[Andreas]

I recompiled with sources version 2.0.0.2 (SuSE AMD Athlon 64, GCC 4.1.0, using the combination found at swiftfox.com). The application calls itself "Bon Echo" now. Don't know why. It does not crash with the extensions I used before.

So I guess the frequent crashes of the Firefox for Linux/X86_64 must have to do with a combination of compiler and/or configure settings?

<code>
Configure settings:
./configure --with-pthreads --enable-application=browser --enable-default-toolkit=gtk2 --with-distribution-id=MyFirefox --disable-freetype2 --enable-single-profile --enable-extensions=default,xforms,schema-validation --disable-installer --disable-tests '--enable-optimize=-O3 -march=athlon64 -freorder-blocks -fno-reorder-functions -msse2 -mmmx -m3dnow -mfpmath=sse -D_FORTIFY_SOURCE=2' --disable-shared --enable-static --disable-profilesharing --disable-debug --enable-xft --enable-crypto --enable-svg --enable-canvas --enable-update-packaging --enable-xinerama --prefix=/usr/local/firefox2
</code>

Comment 4

[Matthias Versen [:Matti]]

You are crashing sometimes, somewhere - that are much informations.
We need either steps to reproduce (which you can not give) or a stacktrace.
If Talkback doesn't come up you have to use your system debugger tools to get a stack trace

Comment 5

[Andreas]

Matthias,

the question is: Why was FF stable until a certain version (very stable, indeed) and is very unstable starting with a new branch? I frequently use FF with MS Windows XP at work, and no such problems. The range of installed plug-ins is the same with my work installation and the one on my personal computer.

I already provided lots of detail infomation; just read it.

Why is talkback disabled in the SuSE versions?

-- Andreas

Comment 6

[Matthias Versen [:Matti]]

Talkback only works for original Mozilla.org builds because because the Talkback server needs the symbols from the build. You have to use the debug tools from Suse if you have a Suse build.

Why is software unstable if you update it ?
maybe there is a bug in Firefox that you only hit on your system frequently or it's a bug in one of the installed plugins that now crashes or it's a bug in one of your system librarys that is now crashing or it's one of the patches that Suse includes in their Firefox builds.

We can do only something with a stacktrace and that's the reason why we have included an easy way to get such a stack trace with our builds(talkback in FF2 and the new Breakpad in FF3). If you use a build from someone else (Suse, Debian..) you have to use their tools and I can't help with example GDB because I'm a win32 user.

Comment 7

[Wayne Mery (:wsmwk)]

do you still see this problem using FF 3.5 beta**, or FF 3.0 started in safe mode***?

If yes, please comment
If not, please close with resolution set to WORKSFORME or INVALID (if problem was extension or the like)

** http://www.mozilla.com/en-US/firefox/all-beta.html
*** http://support.mozilla.com/en-US/kb/Safe+Mode

Comment 8

[Tyler Downer [He/Him]]

No reply, INCO. Reporter, please reopen this bug if you can see this issue with Firefox 3.5 or later in Firefox Safe Mode (http://support.mozilla.com/kb/Safe+Mode) or a new profile (http://support.mozilla.com/kb/Profiles)