after accepting suggested upgrade to v 3.5.6, firefox won't start anymore

RESOLVED INCOMPLETE

Status

()

Firefox
General
--
critical
RESOLVED INCOMPLETE
8 years ago
7 years ago

People

(Reporter: Ralf Hauser, Unassigned)

Tracking

3.5 Branch
x86
Windows Vista
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [CLOSEME 2011-2-25])

(Reporter)

Description

8 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; Trident/4.0; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.5.30729; InfoPath.2; .NET CLR 3.0.30729)
Build Identifier: 

even in safe mode, I see only ~23MB of memory used by firefox.exe in the task manager's process overview, but no window ever pops up

Reproducible: Always

Steps to Reproduce:
1. click on "firefox" in programs menu
Actual Results:  
no window shows

Expected Results:  
a window with my home page
(Reporter)

Comment 2

8 years ago
see also Bug 525490 

http://support.mozilla.com/en-US/kb/Basic+troubleshooting#Make_a_new_profile
appears to get it up again - and yes, after having it once started with a new profile, it also starts again with the old profile.

Suggestion: provide some log that informs that a profile problem is the reason
So you say bug 525490 is the same, just a different version?
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2011-2-25]
This bug has had the CLOSEME tag for several weeks and the date in the tag is
far gone. If the reporter can still see this issue, Please retest with Firefox
3.6.x or later and a new profile
(http://support.mozilla.com/kb/Managing+profiles). Then please remove the
closeme tag in the whiteboard, mark the bug against the proper version and
comment on the bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.