Closed
Bug 677028
Opened 13 years ago
Closed 13 years ago
Crash Reporter restarts Firefox with a different profile, instead of the one specified on the command line
Categories
(Toolkit :: Crash Reporting, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 391977
People
(Reporter: vitar, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0a2) Gecko/20110805 Firefox/7.0a2 Build ID: 20110805042003 Steps to reproduce: Two Firefox version installed side-by-side -- the latest legacy 3.6 installed as a regular app and Aurora 7.0a2 (2011-08-05) installed and used in the Portable Apps variant (with its own launcher and profile and a command line pointing to a profile location). The commandline looks like "path-to\firefox.exe" -profile "Some Path" -no-remote Aurora crashed and popped out a "Submit Crash" request. After "Send report and Restart" a Crash Reporter says "sent ok" and restarts Firefox. Actual results: Now starts THE SAME Aurora (not a legacy 3.6) BUT it uses a legacy profile -- because an app environment contains no commandline parameters. Expected results: A Crash Reporter relaunched a crashed app should preserve a previous environment (in my case it's a "-profile C:\SomePath -no-remote" commandline parameter)
Updated•13 years ago
|
Component: General → Breakpad Integration
Product: Core → Toolkit
QA Contact: general → breakpad.integration
Comment 1•13 years ago
|
||
This is true. I'm not sure it's worth the complexity to fix it, though.
Summary: Crash Reporter loses environment → Crash Reporter restarts Firefox with a different profile, instead of the one specified on the command line
Updated•13 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Need to re-check a dup state because of this bug behavior happens with a CrashReporter ONLY while any other ways to restart (from an Extension Manager or via some extension or via direct chrome: call from a JS Console) works right.
You need to log in
before you can comment on or make changes to this bug.
Description
•