464813 - Firefox crashes frequently with SIGABRT in PR_GetAddrInfoByName

Status: VERIFIED DUPLICATE of bug 463101

(Firefox :: General, defect)

Description

[Mark Aiken]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.3) Gecko/2008101315 Ubuntu/8.10 (intrepid) Firefox/3.0.3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.3) Gecko/2008101315 Ubuntu/8.10 (intrepid) Firefox/3.0.3

After upgrading from Ubuntu Hardy to Intrepid, Firefox 3.0.3 is now very unstable and exits frequently with SIGABRT. Under regular use, I haven't yet seen the browser go more than ~15 mins without crashing. This seems to always happen under a call to PR_GetAddrInfoByName -> getaddrinfo.

Firefox is the 3.0.3 Ubuntu Intrepid package:

maiken@maikendev:~$ sudo apt-cache policy firefox-3.0
firefox-3.0:
  Installed: 3.0.3+nobinonly-0ubuntu2
  Candidate: 3.0.3+nobinonly-0ubuntu2
  Version table:
 *** 3.0.3+nobinonly-0ubuntu2 0
        500 http://us.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
maiken@maikendev:~$ uname -a
Linux maikendev 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:20 UTC 2008 i686 GNU/Linux
maiken@maikendev:~$ lsb_release -rd
Description:	Ubuntu 8.10
Release:	8.10

See also these Ubuntu bugs:

https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/282287
https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/294344

The crashing URL is NOT consistent. My browser crashed immediately when loading the repro URLs from the two referenced bugs (http://www.liliputing.com/2008/10/hp-2133-mini-note-prices-continue-to-drop.html and http://planet.mozilla.org/), but loading them subsequently hasn't caused a crash. So, no solid repro scenario.

I suspect this is the same crash as this bug:

https://bugzilla.mozilla.org/show_bug.cgi?id=463101

...but that bug seems to have gotten titled and bucketed on a red herring (the "double free or corruption" report, which looks like it was spurious)

Reproducible: Couldn't Reproduce

Comment 1

[Mark Aiken]

Attachment: GDB session from a recent crash

Backtraces for SIGABRT crash

Comment 2

[timeless]

sorry. i do appreciate second attempts, but it's better to try to fix the summary of the first bug. especially since the triager is unlikely to change.

Comment 3

[Mark Aiken]

Fine to consolidate the bugs, although please note I am not the submitter of #463101.