Bug 452509 - Firefox randomly crashes with segmentation fault in gmail.
Firefox randomly crashes with segmentation fault in gmail.
Status: CLOSED DUPLICATE of bug 447444
Product: Fedora
Classification: Fedora
Component: firefox (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Gecko Maintainer
Fedora Extras Quality Assurance
Depends On:
Blocks: F10Blocker/F10FinalBlocker F10Alpha/F10AlphaBlocker
  Show dependency treegraph
Reported: 2008-06-23 10:00 EDT by Nikolay Vladimirov
Modified: 2018-04-11 10:10 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-07-23 12:37:44 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
full stack trace (12.18 KB, text/plain)
2008-06-23 10:00 EDT, Nikolay Vladimirov
no flags Details

  None (edit)
Description Nikolay Vladimirov 2008-06-23 10:00:49 EDT
Description of problem:
Firefox crashes with segmentation fault in gmail. It's mostly random. One time
it displays a letter the other it segfaults.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Try to read some letters in gmail

Actual results:

Expected results:
normal operation

Additional info:
This is a tricky one. I'm havin all sorts of firefox crashes. And I can't
reproduce any of them. It just crashes in gmail more often. I guess it doesn't
matter what extentions I use since the stack trace attached is from ff in safe
I removed nspluginwrapper in case it's flash realted .
Comment 1 Nikolay Vladimirov 2008-06-23 10:00:50 EDT
Created attachment 310030 [details]
full stack trace
Comment 2 Hans de Goede 2008-07-21 17:01:12 EDT
I'm also seeing random firefox crashes all over the place in a fully up2date
x86_64 rawhide. One guaranteed way of reproducing it for me is opening:

[hans@localhost ~]$ firefox http://bugzilla.livna.org/show_bug.cgi?id=2057
/usr/lib64/firefox-3.0.1/run-mozilla.sh: line 131:  3116 Segmentation fault     
"$prog" ${1+"$@"}
[hans@localhost ~]$

Involved versions:

Additonal info:
I also got an abort once from glibc's malloc memory checking which backtrace
started at libhunspell, while libhunspell was doing a malloc, so chances are its
innocent, but still I thought it would be good to add a note about this.
Comment 3 Hans de Goede 2008-07-21 17:04:24 EDT
Making this block F10Alpha, as discussed in #fedora-devel
Comment 4 Will Woods 2008-07-22 10:32:34 EDT
Problem sighted on i386 as well.
Comment 5 Matěj Cepl 2008-07-22 10:40:11 EDT
Try to switch off your accessibility functionality (unless you actually need it)
and retest. DOes it help?
Comment 6 Will Woods 2008-07-22 10:45:40 EDT
The hunspell crash is tracked as bug 447444. 
Comment 7 Hans de Goede 2008-07-22 10:56:47 EDT
(In reply to comment #5)
> Try to switch off your accessibility functionality (unless you actually need it)
> and retest. DOes it help?

Not for the livna bugzilla url, I have managed to open that url in firefox
sometimes if another tab was already open, but whne I start firefox with that
url as initial url it crashes constanly (for me).

Maybe this is a race condition and related to smp systems? What I'm thinking is
that since on an smp system 2 threads can run at once, if there is a race the
chance of triggering it is much bigger with smp.
Comment 8 Nikolay Vladimirov 2008-07-22 13:19:08 EDT
Couldn't reproduce this. I'm now using firefox-3.0.1-1.fc10.x86_64. 
I also disabled accessibility. Not sure if it's fixed or not. It crashed randomly. 
So this can be closed. And if firefox continues to crash I'll get backtraces and
submit them and reopen the bug if the crash is related. 
Comment 9 Will Woods 2008-07-23 12:37:44 EDT
This seems fine for me, using xulrunner- (which should fix
ff3-crash-hunspell). caillon suspects this is a dup of that bug, so I'm going to
close it as such.

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

Note You need to log in before you can comment on or make changes to this bug.