345695 - 32-bit SM crashes on startup on 64-bit Windows

Status: RESOLVED INCOMPLETE

(Core Graveyard :: GFX: Win32, defect)

Description

[Eyal Rozenberg]

Although my installation of sm on my Windows 2003 Server 64 bit did not crash on startup initially, it has begun to do so for an unexpected reason. Clearing the profile dir and the installation dir, and reinstalling, does not help.

Using a nightly from 2006-07-23.

Comment 1

[Eyal Rozenberg]

Bug does not manifest with sm 1.0.2 .

Comment 2

[Eyal Rozenberg]

Talkback ID TB21335102W

Stack:

USP10.dll + 0x3fd54 (0x754cfd54)
LPK.DLL + 0x3458 (0x7dbc3458)
GDI32.dll + 0x1622b (0x7d81622b)
GDI32.dll + 0x17359 (0x7d817359)
GDI32.dll + 0x19da9 (0x7d819da9)
USER32.dll + 0x2651f (0x7d95651f)
USER32.dll + 0x27612 (0x7d957612)
USER32.dll + 0x27b9b (0x7d957b9b)
USER32.dll + 0x355b2 (0x7d9655b2)
nsSplashScreenWin::ThreadProc  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpfe/bootstrap/nsNativeAppSupportWin.cpp, line 629]

Comment 3

[Chris Thomas (CTho) [formerly [e-mail] [e-mail]]]

Based on where you crash and what splash screen code I've touched, I'm pretty sure this isn't mine.  I think local variables would be helpful.  Do you have access to a debug environment?

Can you narrow down a regression window?  Is this a 64 bit build of SeaMonkey, or a 32 bit build on a 64 bit OS?

Comment 4

[[e-mail]]

Based on the stack trace, this is the code that is crashing:
    DialogBoxParam( GetModuleHandle( 0 ),
                    MAKEINTRESOURCE( IDD_SPLASH ),
                    HWND_DESKTOP,
                    (DLGPROC)DialogProc,
                    (LPARAM)splashScreen );
Perhaps you've got some corrupt resources somehow...

Comment 5

[Eyal Rozenberg]

It's a 32-bit nightly trunk build. Will try to narrow down the date today.

PS - sm 1.0.2 crashes if I try to search google using the address bar, don't know if that's related.

Comment 6

[Eyal Rozenberg]

Seeing crash with trunk nightly 2006-01-01:

Talkback ID TB21433668X
Stack:

msvcrt.dll + 0x48cc3 (0x77be8cc3)
msvcrt.dll + 0x23148 (0x77bc3148)
msvcrt.dll + 0x27d8d (0x77bc7d8d)
msvcrt.dll + 0x27dd1 (0x77bc7dd1)
PR_GetEnv  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/nsprpub/pr/src/misc/prenv.c, line 82]
nsComponentManagerImpl::GetServiceByContractID  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpcom/components/nsComponentManager.cpp, line 2233]
nsGetServiceFromCategory::operator()  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpcom/components/nsComponentManager.cpp, line 244]
nsCOMPtr_base::assign_from_helper  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpcom/build/nsCOMPtr.cpp, line 150]
nsComponentManagerImpl::LoaderForType  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpcom/components/nsComponentManager.cpp, line 2696]
nsFactoryEntry::GetFactory  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpcom/components/nsComponentManager.cpp, line 3571]
nsComponentManagerImpl::CreateInstanceByContractID  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpcom/components/nsComponentManager.cpp, line 1803]
nsComponentManagerImpl::GetServiceByContractID  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpcom/components/nsComponentManager.cpp, line 2233]
CallGetService  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpcom/build/nsComponentManagerUtils.cpp, line 95]
nsAppStartupNotifier::Observe  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/embedding/components/appstartup/src/nsAppStartupNotifier.cpp, line 99]
main1  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpfe/bootstrap/nsAppRunner.cpp, line 1074]
main  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpfe/bootstrap/nsAppRunner.cpp, line 1740]
WinMain  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpfe/bootstrap/nsAppRunner.cpp, line 1764]
kernel32.dll + 0x26e1a (0x7d4e6e1a)

Comment 7

[Eyal Rozenberg]

The crash occurs with all sm nightlies available from ftp.mozilla.org. 

Comment 8

[Chris Thomas (CTho) [formerly [e-mail] [e-mail]]]

(In reply to comment #7)
> The crash occurs with all sm nightlies available from ftp.mozilla.org. 
> 

Has anyone else encountered this?

Comment 9

[Chris Thomas (CTho) [formerly [e-mail] [e-mail]]]

(In reply to comment #8)
> (In reply to comment #7)
> > The crash occurs with all sm nightlies available from ftp.mozilla.org. 
> > 
> 
> Has anyone else encountered this?
> 

Note that all of my personal builds crash on startup, but not with your stack.

Comment 10

[Eyal Rozenberg]

(In reply to comment #8)
> Has anyone else encountered this?
> 

Let's restate the question: Has anyone had nightlies _not_ crash in recent months with Windows on an AMD x86_64 processor?

Comment 11

[Michael Hendy (Hendikins)]

No crash using latest trunk nightly in the Windows XP x64 Virtual machine I just set up to test this. Clean Windows installation, no other software aside from VMware Tools.

Comment 12

[Eyal Rozenberg]

I just wanted to emphasize that we're talking about the 32-bit nightlies on 64-bit windows.

Also, my mobo is Asus  M2NPV-VM with nVidia GeForce 6150 on-board graphics. If that matters any.

Comment 13

[Chris Thomas (CTho) [formerly [e-mail] [e-mail]]]

(In reply to comment #7)
> The crash occurs with all sm nightlies available from ftp.mozilla.org. 
> 

Comment 2 and comment 6 are different stacks.  Are you sure you have one specific crash that's happening a lot (or at least a very small number of crashes)?  Did you manage to narrow down a regression range?  Is your CPU heatsink dusty?

Hendikins did use an official 32-bit nightly: http://www.hendikins.id.au/screenshots/mozilla/seamonkey-winxp64-20060806.png

Comment 14

[Eyal Rozenberg]

(In reply to comment #13)
> Comment 2 and comment 6 are different stacks.  Are you sure you have one
> specific crash that's happening a lot (or at least a very small number of
> crashes)?

No, I'm not sure. Maybe there are several crashes in different builds. I'll post a stack from the earliest availabe sm nightly.


> Did you manage to narrow down a regression range?

It's not a regression - at least not with respect to sm nightlies. It happens with all sm nightlies available from http://ftp.mozilla.org/ . If there's a source for downloading earlier nightlies, let me know.

>  Is your CPU heatsink dusty?

Not at all, temperature is just fine... should I check my household wiring too? :-(

Comment 15

[Eyal Rozenberg]

See stack of crash of build 2005-07-05-06 in talkback TB21933831W.

Comment 16

[Wayne Mery (:wsmwk)]

Eyal comment #15
> See stack of crash of build 2005-07-05-06 in talkback TB21933831W.

talkback report is expired. 

Comment 17

[Eyal Rozenberg]

(In reply to comment #16)
> talkback report is expired. 

Well, I can't help it. Not using Win64 atm...