532427 - setup.exe spawned by 7zip selfextracting package (win32 3.5.6 candidate build3 signed) crashes with drwatson

Status: RESOLVED INCOMPLETE

(Firefox :: Installer, defect)

Description

[abittner]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.6) Gecko/20091201 Firefox/3.5.6 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.6) Gecko/20091201 Firefox/3.5.6 (.NET CLR 3.5.30729)

i had normal final retail 3.5.5 firefox on winxp prof. english sp3. i first tried the unsigned 3.5.6 candidate build3 today (en-us, win32) installer
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/3.5.6-candidates/build3/unsigned/win32/en-US/Firefox%20Setup%203.5.6.exe
and installed it over my 3.5.5

everything worked normally.

then later today the signed build of 3.5.6 candidate build3 appeared at:
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/3.5.6-candidates/build3/win32/en-US/Firefox%20Setup%203.5.6.exe

and i took that and installed ot over the previously unsigned build.

still during this 7zip selfextracting package and the setup.exe process spawned from there crashed somewhere during the last clicks when clicking through the install wizard where it asks you if you want to do standard install, customized, or where to install it or if you wana start firefox after it has been installed.

actually this last step (and the actual install procedures) never happened, as i think it crashed right before the last step it asks you before it starts copying and extracting files and doing the post-install (housekeeping string?) stuff.

i think my mouse (optical ****) was a bit jumpy and i might have clicked twice on this last "next" button in the installer screens or maybe slightly next to the button or something, the usability at this last "next" dialog felt a bit awkward and so the drwatson crash came up. no crashreporter or anything as it wasnt inside firefox yet ofcourse. maybe debugging such setup/installer problems would also call for better debugging methods and some kind of more global crashreporter for all kinds of components of the mozilla apps in general, if thats feasible. anyways, so i have found the "drwtsn32.log" logfile at "C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson"

here are some details:

Application exception occurred:
        App: C:\DOCUME~1\user01\LOCALS~1\Temp\7zS40D.tmp\setup.exe (pid=2492)
        When: 12/2/2009 @ 17:05:16.590
        Exception number: c0000005 (access violation)

*----> System Information <----*
        Computer Name: PUTER
        User Name: user01
        Terminal Session Id: 0
        Number of Processors: 2
        Processor Type: x86 Family 15 Model 75 Stepping 2
        Windows Version: 5.1
        Current Build: 2600
        Service Pack: 3
        Current Type: Multiprocessor Free
        Registered Organization: 
        Registered Owner:  

*----> Task List <----*
   0 System Process
   4 System
1056 smss.exe
1144 csrss.exe
1176 winlogon.exe
1220 services.exe
1232 lsass.exe
1412 Ati2evxx.exe
1432 svchost.exe
1512 svchost.exe
 344 svchost.exe
 532 svchost.exe
 784 svchost.exe
 896 Ati2evxx.exe
1072 spoolsv.exe
1992 svchost.exe
2020 schedul2.exe
 224 mDNSResponder.exe
 972 jqs.exe
1940 GoogleCrashHandler.exe
1728 svchost.exe
 620 WinVNC4.exe
3512 alg.exe
2248 Explorer.EXE
2696 fpassist.exe
2816 schedhlp.exe
3032 RTHDCPL.EXE
2640 jusched.exe
1892 ctfmon.exe
2680 HotSwap!.EXE
3040 svchost.exe
3052 MOM.exe
3072 cmd.exe
3104 btdna.exe
3164 GoogleToolbarNotifier.exe
3224 DynTray.exe
 732 bash.exe
2376 ccc.exe
1968 bash.exe
1928 bash.exe
3092 procexp.exe
2924 bash.exe
1936 filemon.exe
3688 squid.exe
3748 squid.exe
4068 unlinkd.exe
1556 cmd.exe
 396 Explorer.EXE
5096 cmd.exe
 184 avgtray.exe
 828 avgwdsvc.exe
5116 avgrsx.exe
5640 avgemc.exe
5736 avgcsrvx.exe
3796 putty.exe
4708 Firefox Setup 3.5.6.exe
2492 setup.exe
4576 dwwin.exe
1920 drwtsn32.exe

*----> Module List <----*
(0000000000400000 - 0000000000457000: C:\DOCUME~1\userXY\LOCALS~1\Temp\7zS40D.tmp\setup.exe
(0000000010000000 - 0000000010008000: C:\DOCUME~1\userXY\LOCALS~1\Temp\nsa40F.tmp\StartMenu.dll
(000000005ad70000 - 000000005ada8000: C:\WINDOWS\system32\UxTheme.dll
(000000005cb70000 - 000000005cb96000: C:\WINDOWS\system32\ShimEng.dll
(00000000629c0000 - 00000000629c9000: C:\WINDOWS\system32\LPK.DLL
(000000006f880000 - 000000006fa4a000: C:\WINDOWS\AppPatch\AcGenral.DLL
(0000000074720000 - 000000007476c000: C:\WINDOWS\system32\MSCTF.dll
(0000000074d90000 - 0000000074dfb000: C:\WINDOWS\system32\USP10.dll
(0000000074e30000 - 0000000074e9d000: C:\WINDOWS\system32\RichEd20.dll
(00000000755c0000 - 00000000755ee000: C:\WINDOWS\system32\msctfime.ime
(0000000075f80000 - 000000007607d000: C:\WINDOWS\system32\browseui.dll
(0000000076390000 - 00000000763ad000: C:\WINDOWS\system32\IMM32.DLL
(0000000076780000 - 0000000076789000: C:\WINDOWS\system32\SHFOLDER.dll
(00000000769c0000 - 0000000076a74000: C:\WINDOWS\system32\USERENV.dll
(0000000076b40000 - 0000000076b6d000: C:\WINDOWS\system32\WINMM.dll
(0000000076fd0000 - 000000007704f000: C:\WINDOWS\system32\CLBCATQ.DLL
(0000000077050000 - 0000000077115000: C:\WINDOWS\system32\COMRes.dll
(0000000077120000 - 00000000771ab000: C:\WINDOWS\system32\OLEAUT32.dll
(00000000773d0000 - 00000000774d3000: C:\WINDOWS\WinSxS\X86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.5512_x-ww_35d4ce83\COMCTL32.dll
(00000000774e0000 - 000000007761d000: C:\WINDOWS\system32\ole32.dll
(0000000077920000 - 0000000077a13000: C:\WINDOWS\system32\SETUPAPI.dll
(0000000077b40000 - 0000000077b62000: C:\WINDOWS\system32\Apphelp.dll
(0000000077be0000 - 0000000077bf5000: C:\WINDOWS\system32\MSACM32.dll
(0000000077c00000 - 0000000077c08000: C:\WINDOWS\system32\VERSION.dll
(0000000077c10000 - 0000000077c68000: C:\WINDOWS\system32\msvcrt.dll
(0000000077dd0000 - 0000000077e6b000: C:\WINDOWS\system32\ADVAPI32.dll
(0000000077e70000 - 0000000077f02000: C:\WINDOWS\system32\RPCRT4.dll
(0000000077f10000 - 0000000077f59000: C:\WINDOWS\system32\GDI32.dll
(0000000077f60000 - 0000000077fd6000: C:\WINDOWS\system32\SHLWAPI.dll
(0000000077fe0000 - 0000000077ff1000: C:\WINDOWS\system32\Secur32.dll
(000000007c800000 - 000000007c8f6000: C:\WINDOWS\system32\kernel32.dll
(000000007c900000 - 000000007c9b2000: C:\WINDOWS\system32\ntdll.dll
(000000007c9c0000 - 000000007d1d7000: C:\WINDOWS\system32\SHELL32.dll
(000000007e410000 - 000000007e4a1000: C:\WINDOWS\system32\USER32.dll

*----> State Dump for Thread Id 0x1448 <----*

eax=00000000 ebx=00000001 ecx=7e4189ea edx=00521658 esi=7e41929b edi=00000000
eip=00ae1067 esp=0013d4a4 ebp=0013d4cc iopl=0         nv up ei pl zr na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000246

function: <nosymbols>
No prior disassembly possible
        00ae1067 ??               ???
        00ae1069 ??               ???
        00ae106b ??               ???
        00ae106d ??               ???
        00ae106f ??               ???
        00ae1071 ??               ???
        00ae1073 ??               ???
        00ae1075 ??               ???
        00ae1077 ??               ???
        00ae1079 ??               ???
        00ae107b ??               ???
        00ae107d ??               ???
        00ae107f ??               ???
        00ae1081 ??               ???
        00ae1083 ??               ???
        00ae1085 ??               ???
        00ae1087 ??               ???
        00ae1089 ??               ???
        00ae108b ??               ???
        00ae108d ??               ???
        00ae108f ??               ???
        00ae1091 ??               ???
        00ae1093 ??               ???
        00ae1095 ??               ???
        00ae1097 ??               ???
        00ae1099 ??               ???
        00ae109b ??               ???
        00ae109d ??               ???
        00ae109f ??               ???
FAULT ->00ae1067 ??               ???
Error 0x00000001
        00ae1069 ??               ???
        00ae106b ??               ???
        00ae106d ??               ???
        00ae106f ??               ???
        00ae1071 ??               ???
        00ae1073 ??               ???
        00ae1075 ??               ???
        00ae1077 ??               ???
        00ae1079 ??               ???
        00ae107b ??               ???
        00ae107d ??               ???
        00ae107f ??               ???
        00ae1081 ??               ???
        00ae1083 ??               ???
        00ae1085 ??               ???
        00ae1087 ??               ???
        00ae1089 ??               ???
        00ae108b ??               ???
        00ae108d ??               ???
        00ae108f ??               ???
        00ae1091 ??               ???
        00ae1093 ??               ???
        00ae1095 ??               ???
        00ae1097 ??               ???
        00ae1099 ??               ???
        00ae109b ??               ???
        00ae109d ??               ???
        00ae109f ??               ???
        00ae10a1 ??               ???
        00ae10a3 ??               ???

*----> Stack Back Trace <----*
*** ERROR: Module load completed but symbols could not be loaded for C:\DOCUME~1\userXY\LOCALS~1\Temp\7zS40D.tmp\setup.exe
WARNING: Stack unwind information not available. Following frames may be wrong.
ChildEBP RetAddr  Args to Child              
0013d4a0 00ae10d5 00ae0000 00000000 00390182 0xae1067
0013d4cc 00ae10f2 004021d3 00240166 00000400 0xae10d5
0013dba4 004013ae 0040a0e8 00001154 00401626 0xae10f2
0013e278 004013ae 00436000 00001254 00401626 setup+0x13ae
0013e94c 004013ae 00436000 00175f7c 00404fb9 setup+0x13ae
00000000 00000000 00000000 00000000 00000000 setup+0x13ae
.....

some more raw stackdumps and more two more thread id stuff follows, but its only kernel32 and ntdll or something more general, but i can provide that information if neccessary.

Reproducible: Didn't try

Steps to Reproduce:
1. use ffx 3.5.5 on win32 (winxp, sp3)
2. upgrade with candidate 3.5.6 build3 unsigned
3. upgrade that again with candidate 3.5.6 build3 signed
4. do some nasty click/doubleclicking onto those next buttons in the installer
Actual Results:  
crash of installer (setup.exe)

Expected Results:  
normal install/setup procedure (upgrade install, manually via downloaded .exe installers)

Comment 1

[abittner]

tried some additional bughunting and reproing:

i just took any of the two installer packages from above (doesnt matter if signed or unsigned), as i might have come closer to the source of the bug, although not really being to recreate the crash exactly.

so take the installer (probably doesnt even matter if you have a firefox installed already or not, so most likely works on any clean-install scenario as well) and do:

click next, click custom, click next, destinationfolder is ok, click next, all three checkboxes are already marked, click next, mozilla firefox startmenu group is correct, click next.

then from here on there is this little "checking existing installation" popup kind of window, which seems to be pretty independent from the actual install wizard gui (the screen where you clicked all the stuff and came from), this popup or something seems to be separate thread or subtask, but the real gui beneath this little popup apparently still accepts mouse and keyboard events, so i might have clicked/doubleclicked too often/enthousiastically those next, back and/or cancel buttons or someting.

verifying with processexplorer (msft sysinteral tools or similar helpers) it clearly shows that this additional/accidental clickage  creates hugeloads of additional (sub)threads, i find loads of "banner.dll!destroy+0x14a" threads in the setup.exe process details thread view tab of processexplorer, every additional click seems to create a few threads of these or something.

an additional problem (except for my crash event before) seems to be that these banner.dll thingies "never" finish and terminate at all (at least not like waiting for 5-10mins which i did), so the install never continues from here on.

so this banner.dll stuff might be considered an additional bug, or a bug/behaviour very close to my crash and this original bugreport here. i wonder about this little pest popup stuff and why it needed to be made into an extra separate kind of window of a kind that seems to be somewhat disconnected from the rest of the gui, and leaving the gui reacting to additional/accidental clicks and user-events, which doesnt really make sense at all during this process when the popup shows it checks for existing installation.

this is bad coding or at least usability practice i would say, and i highly suspect the code and internal workflow around this "feature" of the popup window as the main reason for various hangs and crashes.

please do so and get rid of this stuff or at least lock down the gui whenever these kinds of things happen that a user is actually not supposed to be able to create more input events as the program/tastk/process is actually already in the midst of progressing things and working, and then these additionally mistakenly spawned threads render the whole process of installing useless and faulty.

thank and cheers.

http://bayimg.com/DaFEjaAcK

Comment 2

[Robert Strong (they/them - no direct email)]

(In reply to comment #1)
> tried some additional bughunting and reproing:
> 
> i just took any of the two installer packages from above (doesnt matter if
> signed or unsigned), as i might have come closer to the source of the bug,
> although not really being to recreate the crash exactly.
> 
> so take the installer (probably doesnt even matter if you have a firefox
> installed already or not, so most likely works on any clean-install scenario as
> well) and do:
> 
> click next, click custom, click next, destinationfolder is ok, click next, all
> three checkboxes are already marked, click next, mozilla firefox startmenu
> group is correct, click next.
> 
> then from here on there is this little "checking existing installation" popup
> kind of window, which seems to be pretty independent from the actual install
> wizard gui (the screen where you clicked all the stuff and came from), this
> popup or something seems to be separate thread or subtask, but the real gui
> beneath this little popup apparently still accepts mouse and keyboard events,
> so i might have clicked/doubleclicked too often/enthousiastically those next,
> back and/or cancel buttons or someting.
> 
> verifying with processexplorer (msft sysinteral tools or similar helpers) it
> clearly shows that this additional/accidental clickage  creates hugeloads of
> additional (sub)threads, i find loads of "banner.dll!destroy+0x14a" threads in
> the setup.exe process details thread view tab of processexplorer, every
> additional click seems to create a few threads of these or something.
Should be fixed by bug 615131

Are you still able to reproduce?

Comment 3

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 4 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.