Closed Bug 786897 Opened 13 years ago Closed 13 years ago

Command line option -private crashes, if privacy mode is enabled in preferences

Categories

(Firefox :: Private Browsing, defect)

5 Branch
defect
Not set
normal

Tracking

()

RESOLVED FIXED
Firefox 18

People

(Reporter: wamatt, Assigned: Luqman)

References

Details

(Keywords: regression, reproducible)

Attachments

(1 file, 3 obsolete files)

How to reproduce. Step 1. Create a blank profile -no-remote -profile /tmp/temp-profile Step 2. Turn on "Always use private mode" (http://i.imgur.com/4UT7N.png) Step 3. Quit Step 4. Run with -private command line option Crash --- (gdb) run Starting program: /Applications/FirefoxAurora.app/Contents/MacOS/firefox-bin -no-remote -profile /tmp/temp-profile -private Reading symbols for shared libraries . done Program exited with code 06.
Keywords: qawanted
I confirm on Windows that 15.0, 16.0a2, or 18.0a1 don't start with the -private option if the profile is already in permanent browsing mode.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: reproducible
OS: Mac OS X → All
Hardware: x86 → All
Version: 16 Branch → Trunk
It's a regression since Firefox 4 (Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.2a1pre) Gecko/20110330 Firefox/4.2a1pre). Mozregression range m-c good=2011-03-29 bad=2011-03-30 http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=79487686ac29&tochange=2f45c30741c5 Suspected bug: Ehsan Akhgari — Bug 631973 - Opening Firefox in permanent private browsing mode opens an additional window with the home page; r=gavin
Blocks: 631973
Keywords: regression
Keywords: qawanted
Version: Trunk → 5 Branch
CCing some people who might be interested in looking into this crash.
When I tested the regression on Win 7, I met no crash, Firefox just refused to start.
On Linux x64, I got "Program exited normally.". Tried again and get "WARNING: Last startup was detected as a crash.: file /scratch/laden/mozilla-central/toolkit/components/startup/nsAppStartup.cpp, line 1017"
It would be worth figuring out whether bug 631973 is responsible. Try the steps at http://stackoverflow.com/questions/10350661/backout-unwanted-changes-and-make-a-patch-out-of-them to create a patch that reverts the change from that bug, build and see the the problem is still present.
Yep, it does seem like bug 631973 is indeed responsible.
(In reply to Luqman Aden from comment #7) > Yep, it does seem like bug 631973 is indeed responsible. Thanks for the analysis! Can you please try and see if you can fix this? Thanks!
Testing locally with a clean profile seems to indicate that this fixes the issue.
Comment on attachment 657418 [details] [diff] [review] Bug 786897 - Command line option -private crashes, if privacy mode is enabled in preferences. What sayest thou, Ehsan?
Attachment #657418 - Flags: review?(ehsan)
Oops, the autostarted part is needed for the tests.
Attachment #657418 - Attachment is obsolete: true
Attachment #657418 - Flags: review?(ehsan)
Attachment #657493 - Flags: review?(ehsan)
Comment on attachment 657493 [details] [diff] [review] Bug 786897 - Command line option -private crashes, if privacy mode is enabled in preferences. Review of attachment 657493 [details] [diff] [review]: ----------------------------------------------------------------- Looks good. Please also add a comment saying that we don't need to go into PB mode a second time if we're in auto-started mode. Please attach so that we can land this. :-)
Attachment #657493 - Flags: review?(ehsan) → review+
Assignee: nobody → laden
Target Milestone: --- → Firefox 18
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: