Open Bug 680887 Opened 13 years ago Updated 2 years ago

Versions from 3.6.4 - 7b1 not working - no window - only process

Categories

(Firefox :: General, defect)

3.6 Branch
x86_64
Windows 7
defect

Tracking

()

UNCONFIRMED

People

(Reporter: mordek.asg, Unassigned)

Details

Attachments

(4 files)

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1

Steps to reproduce:

Im using Windows 7 Pro x64 and tried to update my old FF (3.6.3) to some newer version.
Version 4 is not working, also 5, 6, 7b1, 8a1. But version 8a1 x64 is runnig very well.

After questions at the #firefox channel I checked more versions between 3.6.3 to 3.6.4, this is the list of working/not working versions:
2010-04-02-05-mozilla-1.9.2 - working
2010-04-03-05-mozilla-1.9.2 - working
2010-04-04-05-mozilla-1.9.2 - working
2010-04-05-05-mozilla-1.9.2 - working
2010-04-06-04-mozilla-1.9.2 - working
2010-04-07-04-mozilla-1.9.2 - working
2010-04-07-10-mozilla-1.9.2 - not working
2010-04-08-04-mozilla-1.9.2 - not working

Of course, tried everything which is in the KB or Ive found at the Internet, I mean:
- cleaning registry
- uninstalling/installing/disabling/enabling my firewall/antyvirus (Windows FW, Eset NOD32 AV)
- running FF with -safe-mode or -profilemanager
- running Windows in safe mode
- and others which I dont remember now :)

Everything gave me same results - running process in Task Manager but no FF window (you can see this at attached firefox.png).

I ran debugger on the firefox.exe process and it looks like its in loop in xul.dll

You can also see what show the ProcMon (firefox.pml - native ProcMon file format).

My graphic card is: NVIDIA GeForce 9600M GT with driver version: 8.17.12.6658


Actual results:

FF show process in task manager but no window.


Expected results:

I should see FF GUI :)
Attached image firefox.png
Attached file firefox.PML
Can you please attach a stacktrace from windbg:
https://developer.mozilla.org/en/How_to_get_a_stacktrace_with_WinDbg

>- running FF with -safe-mode or -profilemanager
Did the profilemanager open ?
And does renaming the firefox.exe make a Difference?
(In reply to XtC4UaLL [:xtc4uall] from comment #4)
> And does renaming the firefox.exe make a Difference?

No, this does not working.

(In reply to Matthias Versen (Matti) from comment #3)
> Can you please attach a stacktrace from windbg:
> https://developer.mozilla.org/en/How_to_get_a_stacktrace_with_WinDbg
> 
> >- running FF with -safe-mode or -profilemanager
> Did the profilemanager open ?

No, profile manager is not opening.
Stacktrace as attachment (I think this is it).
Attached file Stacktrace
I can't find something in the stack trace that would explain that but I'm no expert.
It's possible that some 32bit dll injects itself in the Firefox process and that dll is causing problems.

An example is 
ModLoad: 00f10000 00f5e000   C:\Program Files (x86)\Nokia\Nokia PC Suite 7\bkmrksync\components\BkMrkExt.dll

and

ModLoad: 00e50000 00e92000   C:\Users\mordek\AppData\Roaming\IDM\idmmzcc3\components\idmmzcc.dll
(In reply to Matthias Versen (Matti) from comment #7)
> I can't find something in the stack trace that would explain that but I'm no
> expert.
> It's possible that some 32bit dll injects itself in the Firefox process and
> that dll is causing problems.
> 
> An example is 
> ModLoad: 00f10000 00f5e000   C:\Program Files (x86)\Nokia\Nokia PC Suite
> 7\bkmrksync\components\BkMrkExt.dll
> 
> and
> 
> ModLoad: 00e50000 00e92000  
> C:\Users\mordek\AppData\Roaming\IDM\idmmzcc3\components\idmmzcc.dll

I tried before deinstalling Nokia PCSuite and Internet Download Manager (Ive found that this application can make problems with FF), but no change.

Ive done this now, stacktrace as attachment (firefox-debug_07c8_2011-08-29_21-14-51-409.log).
Attached file New Stacktrace
I can't see any Firefox related Stacktraces at all. Only it being listed as a running Process.

Regarding your Regression Range mentioned in Comment 0, this is the Pushlog:
http://hg.mozilla.org/releases/mozilla-1.9.2/pushloghtml?fromchange=a2ab794bfff4&tochange=ec534329e186

=> Merge of the Lorentz Repo => "Out of Process Plugin" Usage including the "plugin-container.exe".

Does setting "dom.ipc.plugins.enabled" to false in a Profile ran with a (working?) X64 Nightly and after that running a X86 Nightly (what previously failed, right?) make a Difference?

If not I'd suggest to disable *all* non-Microsoft Autostart Stuff and Services for Testing Purposes and repeat.
(In reply to XtC4UaLL [:xtc4uall] from comment #10)
> I can't see any Firefox related Stacktraces at all. Only it being listed as
> a running Process.
> 
> Regarding your Regression Range mentioned in Comment 0, this is the Pushlog:
> http://hg.mozilla.org/releases/mozilla-1.9.2/
> pushloghtml?fromchange=a2ab794bfff4&tochange=ec534329e186
> 
> => Merge of the Lorentz Repo => "Out of Process Plugin" Usage including the
> "plugin-container.exe".
> 
> Does setting "dom.ipc.plugins.enabled" to false in a Profile ran with a
> (working?) X64 Nightly and after that running a X86 Nightly (what previously
> failed, right?) make a Difference?
Nightly x64 is working, with dom.ipc.plugins.enabled == true and dom.ipc.plugins.enabled == false.
The change in profile (in x64) does not help to successful start x86 version of Nightly

> If not I'd suggest to disable *all* non-Microsoft Autostart Stuff and
> Services for Testing Purposes and repeat.
You mean, literally all non-Microsft things? :)
> > If not I'd suggest to disable *all* non-Microsoft Autostart Stuff and
> > Services for Testing Purposes and repeat.
> You mean, literally all non-Microsft things? :)
I disabled everything but no change.
Tried under Windows Safe Mode but also no change.
Weird. I ran out of Ideas to process thus any further :-/.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: