Closed
Bug 287734
Opened 20 years ago
Closed 20 years ago
Firefox 1.0.2 will not launch
Categories
(Firefox :: Installer, defect)
Tracking
()
VERIFIED
INVALID
People
(Reporter: stephen, Assigned: bugs)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) Build Identifier: 1.0.2 Upgraded to critical update 1.0.2 from 1.0.1 and now when I try to launch Firefox there is some disk activity but the application does not launch. Reproducible: Didn't try Steps to Reproduce: 1. Install Firefox 1.0.0 2. Upgrade to 1.0.1 3. Upgrade to 1.0.1 Actual Results: No Firefox window Expected Results: Launched and displayed home page I had noticed that some plugins didn't work in 1.0.1 (e.g. Adblock)
Comment 1•20 years ago
|
||
Did you try to run Firefox in the safemode ?
| Reporter | ||
Comment 2•20 years ago
|
||
(In reply to comment #1) > Did you try to run Firefox in the safemode ? Came in to work this morning and tried it. I got the same thing - lots of disk activity for 5-6 seconds then nothing.
When you launch Firefox, and the disk activity happened, have you opened the Task Manager to see if the process does indeed begin? If the process is running, but nothing appears, that could indicate it is either lagging due to the amount of extensions you have installed, or for some other reason. I don't believe I have ever had it not start, but I have at one point had it take around 3 minutes to start. The fact that disk activity happens indicates to me that the process is being ran, but perhaps there is something either crashing it before it can actually load all the way, or it is loading but not appearing.
| Reporter | ||
Comment 4•20 years ago
|
||
(In reply to comment #3) > When you launch Firefox, and the disk activity happened, have you opened the > Task Manager to see if the process does indeed begin? I haven't had task manager running while trying to launch Firefox but I have looked afterwards and Firefox doesn't appear. FF definitely doesn't come up after an extended period. I will see what happens in task manager during the disk activity on Monday.
| Reporter | ||
Comment 6•20 years ago
|
||
(In reply to comment #5) > Sounds like a plan, because I am unable to reproduce this. firefox.exe does not show up in the Applications pane of Task Manager, but it does appear in the Process pane as using 13,568 K of memory. I don't know if it is connected but the first time Firefox is launched after a reboot, an entry for sysfader appears in the Application pane for a second or so. It doesn't happen on subsequent attempts.
| Reporter | ||
Comment 7•20 years ago
|
||
Update: Tried removing Firefox using Control Panel...Add/Remove Programs, then reinstalling. Same result. Tried removing Firefox, rebboting, then reinstalling. Same thing again. The exact memory usage reported by Task Manager varies a little but is always close to 13 MB.
Comment 8•20 years ago
|
||
(In reply to comment #7) I had this same problem and I uninstalled firefox 1.0.2 using add remove programs and then installed in the same directory Program Files/Mozilla Firefox and got the same results. I just recently created a new profile in start->run->firefox.exe -profilemanager and it seems to be running alot better. Ps. my problems were I could always open one instance of the browser however it would be quite slow, but if I tried to open up another instance it would hang forever even though I could see it trying in the task manager.
| Reporter | ||
Comment 9•20 years ago
|
||
> I just recently created a new profile in
> start->run->firefox.exe -profilemanager and it seems to be running alot better.
>
That did the trick - maybe the default profile was corrupted.
Thanks.
Stephen
Comment 10•20 years ago
|
||
without an understanding of what was corrupted in the first profile, this bug is of no value. If you can compare your two profiles and determine which file or files was causing the problem, please reopen this bug with that information. Thanks.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Updated•19 years ago
|
Status: RESOLVED → VERIFIED
QA Contact: bugzilla → installer
You need to log in
before you can comment on or make changes to this bug.
Description
•