Bug 734018 - firefox-6.0 often crashing on F16 x86_64
Summary: firefox-6.0 often crashing on F16 x86_64
Status: CLOSED DUPLICATE of bug 730856
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 16
Hardware: x86_64
OS: Unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2011-08-29 07:56 UTC by Jens Petersen
Modified: 2011-09-01 02:29 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-09-01 00:16:57 UTC
Type: ---

Attachments (Terms of Use)

Description Jens Petersen 2011-08-29 07:56:55 UTC
Description of problem:
F16 Firefox seems to crash quite often when I am browsing.
A crash dialog appears and the report is sent to mozilla.org.
I thought I better file a fedora bug to track this issue.

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

How to reproduce:
1. Install F16 Alpha Live x86_64
2. Browse around blogs from start page.

Actual results:
Firefox crashes quite often spontaneously while browsing.
I have a feeling that when it crashes it is usually after rendering a page.

Expected results:
No crashes.

Additional info:
I haven't seen crashes under i686 yet.

Comment 1 Jens Petersen 2011-08-30 08:31:37 UTC
I will try an upstream build later to confirm it is not some toolchain issue.

Comment 2 Jens Petersen 2011-08-31 12:24:30 UTC
Hmm after latest yum update today I haven't seen any crashes today.
Maybe newer kernel?  (I am now running kernel-3.1.0-0.rc4.git0.0.fc16.x86_64.)

Comment 3 Adam Williamson 2011-08-31 16:26:44 UTC
This is almost certainly a dupe of #730856, which causes exactly this symptom (sporadic crashing in any app that does lots of DNS lookups, usually observed in Firefox).

Comment 4 Jens Petersen 2011-09-01 00:16:57 UTC
Thanks, Adam - I think you're quite right.

I am back in the office today and had a crash in about 5min.
Strange that it is ok at home but not in the office -
must be some dns difference.

Closing as a duplicate of glibc bug 730856, though dunno if it is
better to keep this open until glibc gets fixed for other people to know.

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

Comment 5 Adam Williamson 2011-09-01 02:29:20 UTC
jens: the bug tends to resist 'patterns' because it happens when you get one of three fairly unusual responses from the DNS server; no DNS server is very likely to give out these responses _consistently_ over a long period, but most servers will give one of them out every so often, sometimes for - say - 15 minutes for a particular domain...so you think you have a reproducer, you go have lunch, and suddenly it's not a reproducer any more...

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