Closed Bug 601145 Opened 14 years ago Closed 14 years ago

Mac64 builds from today won't start when using profile manager

Categories

(Toolkit :: Startup and Profile System, defect)

x86_64
macOS
defect
Not set
normal

Tracking

()

VERIFIED FIXED
mozilla2.0b7
Tracking Status
blocking2.0 --- beta7+

People

(Reporter: u279076, Assigned: jaas)

References

Details

(Keywords: regression)

Attachments

(2 files, 1 obsolete file)

Today's mozilla-central nightlies (2010-10-01) will not start using the profile manager. 1. firefox-bin -P -no-remote 2. select a profile or create a new one 3. Start 4. select a profile or create a new one 5. Start 6. repeat...repeat...repeat... Result: Firefox is stuck in a loop at the Profile Manager Expected: Firefox starts with the profile, or at least give me an error.
Yesterday's build is fine: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b7pre) Gecko/20100930 Firefox/4.0b7pre
blocking2.0: --- → ?
Keywords: regression
> Apparently, the source stamp is: > http://hg.mozilla.org/mozilla-central/rev/a60414d076b5 That's surprising, as that's Wed, Sep 29 and someone said the builds from the 30th are fine. I suspect bug 600411.
blocking2.0: ? → beta7+
Component: General → Startup and Profile System
Product: Firefox → Toolkit
QA Contact: general → startup
Assignee: nobody → joshmoz
I am not sure if since Bug 600411 was fixed whether or not a new 10.5 build is supposed to launch as well, but the same thing happens using a 10.5 build when I download the latest nightly. There are a number of errors in the console that I can paste if it is helpful.
I can confirm that bug 600411 caused this. Backing it out fixes the problem.
I just hit what is probably the same problem while working on the crashreporter patch. The problem is that you're passing NULL as the last param of posix_spawnp, so the child process gets an empty set of environment variables. You can pass *_NSGetEnviron() (after #include <crt_externs.h>) to copy the current process' environment.
Summary: Mac64 builds from today won't start → Mac64 builds from today won't start when using profile manager
(also the restart process uses environment variables to pass state, which is why this is happening.)
May not be useful, but adding in case it is.
Attached patch fix v1.0 (obsolete) — Splinter Review
Attachment #480163 - Flags: review?(ted.mielczarek)
I wonder if we want to propagate environment variables to things launched by nsIProcess. My patch for bug 600711 does not propagate them.
Attachment #480163 - Flags: review?(ted.mielczarek) → review+
Attached patch fix v1.1Splinter Review
This is a little safer, checks pointer from _NSGetEnviron before derefing it.
Attachment #480163 - Attachment is obsolete: true
Attachment #480167 - Flags: review?(ted.mielczarek)
Attachment #480167 - Flags: review?(ted.mielczarek) → review+
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
(In reply to comment #4) > I am not sure if since Bug 600411 was fixed whether or not a new 10.5 build is > supposed to launch as well Bug 600411 only fixed one of the cases where a 10.5 build would crash (restart triggered from the app). 10.5 builds still crash before and after the update is applied (bug 600777, bug 600362).
Verified fixed with Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b7pre) Gecko/20101002 Firefox/4.0b7pre
Status: RESOLVED → VERIFIED
Target Milestone: --- → mozilla2.0b7
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: