Closed Bug 501424 Opened 15 years ago Closed 15 years ago

crash on startup after upgrade from 3.0.11 to 3.5 [@ nsDocShell::SetupNewViewer(nsIContentViewer*) ]

Categories

(Firefox :: General, defect)

3.5 Branch
x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 434403

People

(Reporter: iiridayn, Unassigned)

Details

(Keywords: crash, crashreportid)

Crash Data

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.17) Gecko/20080829 Firefox/2.0.0.17
Build Identifier: http://download.mozilla.org/?product=firefox-3.5&os=win&lang=en-US

Deleted profile, uninstalled all extensions, using the downloaded binary installer or the Help->Check for Updates option, once Firefox 3.5 has been installed, it crashes.

Reproducible: Always

Steps to Reproduce:
1. Install Fx 3 on my system
2. Upgrade to or install Fx 3.5
3. Submit crash report
Actual Results:  
Firefox produces the crash screen, no browser window

Expected Results:  
Firefox works like a charm

Some crash IDs:
Crash ID: bp-cbf40ae0-349f-4b1d-82c1-ae1762090630
Crash ID: bp-66037d19-e950-4eb6-a3e7-dfa8c2090630
Crash ID: bp-193d970a-2206-4111-9f92-fc69b2090630
Crash ID: bp-35bdc7d8-eacd-4f19-86ed-2671e2090630
Crash ID: bp-6bc2fad4-07e6-414f-97d1-699da2090630
Crash ID: bp-4f703a8c-638c-41aa-81ad-e5d4c2090630
Crash ID: bp-3e833e1c-0b0c-486b-ab8a-da3f92090630
Crash ID: bp-0c12d15b-2046-4b32-8f5c-822502090630
Flags: blocking-firefox3.5?
Keywords: crash, crashreportid
Version: unspecified → 3.5 Branch
OK, so when does it crash? Immediately after you start, or after you have done some browsing? Does it happen when you try to start in Safe Mode? Will have to wait until your crashes are processed to figure this out a bit more.
Immediately after it starts - I clicked through the first crash id, and it reported the method as nsDocShell::SetupNewViewer(nsIContentViewer*) - I know that it crashes before any window of any kind is displayed, which makes sense given the  point of error.
Summary: crash on startup after upgrade from 3.0.11 to 3.5 → crash on startup after upgrade from 3.0.11 to 3.5 [@ nsDocShell::SetupNewViewer(nsIContentViewer*) ]
Started up in safe mode - same result:
Crash ID: bp-6e8e2161-713c-40d3-ac21-433ae2090630
transferring blocking flag
Flags: blocking-firefox3.5? → blocking1.9.1.1?
Had you used a previous version of Firefox 3.1/3.5?
Confirming this due to there being over 1,000 crashes here and I'm assuming someone meant to confirm this since the blocking flag was set.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Looks very similar to bug 434403.

Please locate file svrltmgr.dll on your computer. This file is associated with software provided by SpectorSoft which is known to be problematic. If your copy of that isn't provided by SpectorSoft then submit it to http://virusscan.jotti.org/
(In reply to comment #5)
> Had you used a previous version of Firefox 3.1/3.5?

Yes.  Fx 3.5 RC2 had the same symptoms, but I didn't report them at the time.


(In reply to comment #7)
> Looks very similar to bug 434403.
> 
> Please locate file svrltmgr.dll on your computer. This file is associated with
> software provided by SpectorSoft which is known to be problematic. If your copy
> of that isn't provided by SpectorSoft then submit it to
> http://virusscan.jotti.org/

Interesting possibility - following up with the IT department.
Followed up with the IT department - we do use Spector.  Other computers in the company have no issue when installing and running Firefox 3.5.  Did the scan, it came up with one hit, to not-a-virus:EBlaster, which is produced by the same company, so it's very probably correct.  When file is renamed, Fx doesn't crash - however, it warns that it will not run because another instance is running already (despite a fresh reboot).

This is similar to the first behavior, in which Firefox 3.5 would require a reboot before running - and rebooting wouldn't remove the error (even as the system administrator).  At some point I backed up and deleted my profile and backed up and uninstalled all of my extensions.  I'm currently writing from a portable copy of Fx 2.
Have read all contents of bug 434403.  Yes, it seems to be a duplicate of that bug, and most probably the fault of Specter.  The only thing that I find frustrating is that most other computers in the company can run the new version, though I am increasingly suspecting that as a result of local system configuration more than anything else.  Unfortunately this issue has taken up too much of my day already.  I will bring it up with the IT staff at some later time, once a larger portion of the users in the company have been updated to the latest Firefox version.

As a side note, it'd be excellent if Fx has some kind of test and throws an error message indicating a possible conflict with snooping software or viruses of some kind - though it's not an obligation.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
had the same problem on Vista Home Premium 32 bit. FF3.5 crashed at start up. Even after a clean install. No addons and no profiles. FF3.5 only runs normally when opened with the "Run as Administrator" option. I do use Spectersoft software.
(In reply to comment #12)
> had the same problem on Vista Home Premium 32 bit. FF3.5 crashed at start up.
> Even after a clean install. No addons and no profiles. FF3.5 only runs normally
> when opened with the "Run as Administrator" option. I do use Spectersoft
> software.

Please contact your IT for further help as the software is installed to monitor browsing while at work (or personal use also).
Flags: blocking1.9.1.1?
Crash Signature: [@ nsDocShell::SetupNewViewer(nsIContentViewer*) ]
You need to log in before you can comment on or make changes to this bug.