Closed Bug 666657 Opened 10 years ago Closed 10 years ago

segfault when running firefox without -no-remote (with a Firefox instance already running)

Categories

(Toolkit :: Startup and Profile System, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

VERIFIED FIXED
mozilla7

People

(Reporter: dholbert, Assigned: glandium)

References

Details

(Keywords: regression)

Attachments

(1 file)

STEPS TO REPRODUCE:
 1. Start a Nightly build from 110618 or more recent.
 2. In another terminal, run that nightly build again. e.g.
     [~/myNightly]$ ./firefox

ACTUAL RESULTS: segfault. (The text "Segmentation fault" is printed before command returns to my terminal)  Other than that, everything seems normal. (A new firefox window appears, as I'd expect.)

EXPECTED RESULTS: No segfault.
Nightly regression range:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=306bdc7101c3&tochange=0830b8ed9f02

In that range, my first suspect would be bug 552864 -- tentatively flagging as regression from that.
Mozilla/5.0 (X11; Linux x86_64; rv:7.0a1) Gecko/20110622 Firefox/7.0a1
Ubuntu 11.04 x86_64
Component: General → Startup and Profile System
Product: Core → Toolkit
QA Contact: general → startup
Most likely cause is something accessing a static string after libxul is unloaded. Not the first time this happens, I've fixed a bunch of those a while ago.
Not tested, but this should work. I would like to add a test that would basically do firefox -remote 'ping()' and check that we get a return value of 2 and not 139, but I'm not sure where to put that...
Attachment #541558 - Flags: review?(benjamin)
Attachment #541558 - Flags: review?(benjamin) → review+
Assignee: nobody → mh+mozilla
http://hg.mozilla.org/mozilla-central/rev/53a8eddbd9a4
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Whiteboard: [inbound]
Target Milestone: --- → mozilla7
Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20100101 Firefox/7.0

Verified Fixed on Ubuntu 11.04 using the steps in Comment 0. No "segfault" is displayed anymore when running the second instance.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.