Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.
I am not sure of your exact hanging or zombie problems with FF3, although there is a know issue with FF3 that it takes a while for the firefox.exe process to terminate after closing down the browser. This is not a fault of N360. Here is a Mozilla Knowledge Base article that deals with 'hanging' in FF3. Link . Here is the link for Mozilla support, I would also look there and even submit an issue to Mozilla about it Link .
Here is another thread on here with similar problems Link.
I don't even like the new FF3, and I think I will go back to FF2. If you decide to do the same, here is the direct link to FF2. Link
Good luck!!!
Have you seen a thread about anyone else having an issue with the closure of firefox 3 ?
If the zombie fix is not working for you, then it is reasonable to assume that firefox is not being hung by the same dll that affects others. It would seem therefore worthwhile either running debugging tools or DR Watson against the pid of the firefox process and establishing perhaps with Microsoft what is hanging firefox from closure.
I am sure that this problem is caused by Norton. I have been using firefox 3.0 since its release, and just yesterday upgraded to norton 360 2.0. I did not have this issue until AFTER the upgrade. There is nothing else that I have done since to cause this problem. I did read about an issue with AppMgr32.dll creating hooks and not releasing them. I am only reading that from a website and dont really understand it, but perhaps its worth a second look, as it sounds plausible to me. Here is a link to the site I looked at.
http://forum.sysinternals.com/forum_posts.asp?TID=15105&PN=2
The posting to which you refer is from me. I am goldman, cgoldman, cgoldman3 and whatever else I cant remember.
As a result of bringing the issue to this forum, and then labeling that issue as "zombie", a workaround has been posted.
The deregistration of the bushell.dll release the other dll. At least that is my understanding. In any event you have applied the workaround and I accept that it does not resolve your issue. That is why, I am suggesting further steps that you could take.
I am not saying it is not Norton but perhaps it is not the same problem that generally affected other zombie processes.
Maybe a staff member will drop by and provide further instructions.
>>Here is the link for Mozilla support, I would also look there and even submit an issue to Mozilla about it Link .>>
Have you tried this, it may just help us to resolve this issue for you?
Thanks for the direction. Interesting article. I think these links were already given by you in message 2 of this thread.
My problem is that it requires a significant investment of time to even understand the real problem here. People say hang when they mean crash, and then say "they are not recognised by windows..".
It would surely help if blab 357 would post loads more details about his issue. Why and how does he ascribe it as a zombie process.
Has he applied dr watson to the running PID and does Dr Watson then close the zombie? Can he kill the zombie in Windows Task Manager and does the zombie go?
Ungrade was mentioned but not what the AV was before Norton 360 v2. Was NRT involved, should it have been?
I was actually referring more to this on the Mozilla webpage:
I think it is more of a FF issue IMO.
Ah right. See what you mean. Yes, good idea.
Hello cgoldman,
I want to help you understand my situation better so I will provide any information you would like, however I am not familiar with the nitty gritty inner workings. I need you guys to help guide me in the right direction.
I describe it as a zombie process as the .exe is no longer performing any recognizable task. The desktop window is closed but the underlying process is still active and visible in the task manager. If I completely close firefox, so that it is no longer visible in the start bar, then start another instance of the program, a new instance of firefox.exe process is created. This can be repeated pretty much until I run out of ram.
If I leave them alone for an hour, leaving the desktop idle and only background processes running, they do not close on their own. I tried modifying the registry as was described in another thread and it has no effect.
I have not used Dr. Watson at all as I am not familiar with how the program works, however if someone thinks this program could either help me describe my problem or fix it, then I would like to know the proper procedure is.
The situation before a couple of days ago (July 19th) was that I was running a completely up to date version of Norton 360 1.0 but my subscription expired and I decided to spend the extra money and get an upgrade to Norton 360 2.0. Also, since June 17th I have been running Firefox 3.0 and had experienced no problems with it. I proceeded with the update and purchased the software from the online store and installed it successfully.
I then started Firefox as normal and noticed nothing unusual, but after closing firefox and coming back some time later I noticed that my profile would not load when I started the program up again. That means that I had no bookmarks and all my settings had reverted to default. I tried to import all my bookmarks from backup but I found I couldn’t. So I checked the task manager only to find that firefox.exe was running half a dozen times. I terminated them all, then restarted firefox and it runs normally, but only the first time you open it.
If you have any more questions please ask, and I will do my best to answer. Thanks for your help everyone.
I was building up a reply and lost it. Here goes again.
I need to be quite clear.
1. You reboot machine
2. You execute Firefox and exit firefox.
3. Firefox is still running in start bar and is seen in Windows TAsk Manager.
can you right mouse click the icon in start bar and is their an option to close?
How otherwise are you removing Firefox from start bar?
4. You kill process in Windows Task Manager and rerun Firefox.
Does firefox load?
Have I got this right please.
Download and install procexp from here
Rerun 1-4 above, but instead of using WIndows Task Manager use procexp.
Identify application in procexp and right mouse click and select Kill Process Tree (not Kill Process),
Can you now restart Firefox and is there an changes i.e. does it run?
Rerun 1-3 above, run Procexp and before killing job, note number in 2nd column the PID. Do NOT kill process.
run drwtsn32 i.e. start menu, run, enter drwtsn32.exe, click "OK". note full details on the first two entries on the popup.
Check all boxes in the "Options" section of Dr. Watson for Windows when the dialog appears. OK the changes in Dr. Watson.
Hello again.
1. Yes I reboot the machine and it starts fresh.
2. I execute firefox.exe from a shortcut on my desktop
3. I click on the X in the top right
4. The window dissapears, no evidence of it remains on the desktop AT ALL
5. I restart firefox.exe
6. All bookmarks and other profile information is missing and I get a about:blank home page
7. I check task manager, there are 2 firefox.exe's running
8. I close the second instance of firefox from the X in the top right
9. Both processes remain
10. I manually end task on both
11. I restart firefox from shrotcut
12. All profile information is restored
Firefox will restart and run without any profile information an infinite amout of times. I was not clear before in my first post. I realise that I did not mention that the window would come up but the profile information was missing. I am sorry about that. I have no problem terminating the process.
My problem is that a process that should self terminate when the X button is pressed, has stopped doing so and it only started doing this when I upgraded to norton 360 2.0.
Oh and a quick update. I just ran the norton removal tool. Norton is gone. Firefox works.
blab357. I understand precisely the problems you are having with FF3. You are not the first to experience these issues with or without Norton. I know because it was happening with me.
So, you ran the NRT and now you have no N360 but FF seems to be working. Question: When you upgraded to N360v2, did you let the new download uninstall the old version and install v2 automatically, did you upgrade through Live Update, or did you run the Norton Removal Tool to uninstall your previous version of N360, prior to installing N360v2.
Let me know please, thanks. Hang in there!
Thank you for the further information. I do not doubt that your problem has gone when Norton is removed. However, I need you to follow by suggestions very carefully.
I do not want you to start two firefox sessions. I wanted you to start firefox, close it, and if it created a zombie, then kill the zombie process, then start firefox.
However, I must presume that if you manually ended on two firefox processes, and the third execution worked oK, that ending process on one Firefox would also allow Firefox to restart intact.
On this basis you can skip killing the thread with procexp, because it is clear that a simple kill in windows task manager restores
sanity.
It is also most likely that if you can successfully kill the process in Windows Task Manager that Dr Watson would also be able to terminate the PID. The Dr Watson reports would identify the culprit that is hanging Firefox, and I suspect loading Microsoft debugging tools, as I and one other contributor have suggested in another thread, would also identify the issue.
At this point, particularly as you have now removed Norton 360, I suggest you would benefit from a Symantec employee coming to your rescue.
I agree with you, but I would still like to know how he uninstalled V1 of N360, and is this latest time the first time he has run the removal tool.
I had FFV2 installed, upgraded to FF3, and have the same issue where you close the FF browser, and it keeps running in Task Manager. The thing is it should eventually terminate after it cleans up what is has to, HOWEVER, it you try to restart a new instance of FF in the meantime you will start running into trouble. I would suggest waithing for a bit before trying to restart the app, or just kill it in Task Manager if it won't let you back in.
I still say it is a bug with FF3 because the same thing happens on my other system where I have NIS09 Beta installed, and the problem did not occur with FF2.
Have you sumbitted a ticket with Mozilla about this?
Will wait for further advices.
Hi
If this is a timing issue, and if left alone Firefox would eventually exit Windows Task Manager, is there any merit in changing those timing settings (2 & 3) that you clearly set out in your post on another thread?
I see where you are coming fron now, but I think so yes, because if they are involved in this shutdown issue then of course mine would close quicker because I have adjusted those settings. FF doesn’t need all that time to close, it is just hanging around unnecessarily for too long.
Moved forum usage tip to forum feedback.
Here is the Dr.Watson dump....
Application exception occurred:
App: C:\Program Files\Mozilla Firefox\firefox.exe (pid=3288)
When: 7/22/2008 @ 17:27:36.078
Exception number: 80000007
()
*----> System Information <----*
Computer Name: *********
User Name: ********
Terminal Session Id: 0
Number of Processors: 2
Processor Type: x86 Family 15 Model 35 Stepping 2
Windows Version: 5.1
Current Build: 2600
Service Pack: 2
Current Type: Multiprocessor Free
Registered Organization: ********
Registered Owner: ********
*----> Task List <----*
0 System Process
4 System
880 smss.exe
980 csrss.exe
1004 winlogon.exe
1048 services.exe
1060 lsass.exe
1232 svchost.exe
1300 svchost.exe
1424 svchost.exe
1464 svchost.exe
1576 svchost.exe
1668 svchost.exe
1860 ccSvcHst.exe
380 ccProxy.exe
1372 Explorer.EXE
320 spoolsv.exe
1640 AppleMobileDeviceService.exe
1880 AluSchedulerSvc.exe
1932 mDNSResponder.exe
2008 E_S30RP1.EXE
608 nTuneService.exe
600 nvsvc32.exe
688 PnkBstrA.exe
664 RichVideo.exe
960 svchost.exe
2556 alg.exe
2044 CTHELPER.EXE
208 CTXFIHLP.EXE
796 svchost.exe
2252 CTXFISPI.EXE
2480 itype.exe
2504 pptd40nt.exe
2604 gnotify.exe
2624 XboxStat.exe
2632 RUNDLL32.EXE
2748 PDVDServ.exe
2996 brs.exe
3300 iTunesHelper.exe
3372 jusched.exe
3416 ccSvcHst.exe
2564 ctfmon.exe
4076 MsnMsgr.Exe
2144 iPodService.exe
2448 SetpointII.exe
2896 KHALMNPR.EXE
3264 usnsvc.exe
2868 symlcsvc.exe
2288 ntvdm.exe
3288 firefox.exe
3496 firefox.exe
3228 cmd.exe
2012 drwtsn32.exe
*----> Module List <----*
(0000000000400000 - 000000000044d000: C:\Program Files\Mozilla Firefox\firefox.exe
(0000000001180000 - 0000000001186000: C:\WINDOWS\system32\ctagent.dll
(0000000002990000 - 0000000002999000: C:\WINDOWS\system32\Normaliz.dll
(0000000010000000 - 0000000010024000: C:\PROGRA~1\COMMON~1\SYMANT~1\ANTISPAM\ASOEHOOK.DLL
(0000000016080000 - 00000000160a5000: C:\Program Files\Bonjour\mdnsNSP.dll
(0000000020000000 - 00000000202c5000: C:\WINDOWS\system32\xpsp2res.dll
(000000004ec50000 - 000000004edf3000: C:\WINDOWS\WinSxS\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.2600.2180_x-ww_522f9f82\gdiplus.dll
(000000005ad70000 - 000000005ada8000: C:\WINDOWS\system32\uxtheme.dll
(000000005b860000 - 000000005b8b4000: C:\WINDOWS\system32\NETAPI32.dll
(000000005dca0000 - 000000005dce5000: C:\WINDOWS\system32\iertutil.dll
(0000000060000000 - 00000000600ae000: C:\Program Files\Mozilla Firefox\MOZCRT19.dll
(00000000600b0000 - 00000000600e0000: C:\Program Files\Mozilla Firefox\nspr4.dll
(00000000600e0000 - 00000000600e7000: C:\Program Files\Mozilla Firefox\plds4.dll
(00000000600f0000 - 00000000600f7000: C:\Program Files\Mozilla Firefox\plc4.dll
(0000000060100000 - 00000000601ad000: C:\Program Files\Mozilla Firefox\js3250.dll
(00000000601b0000 - 00000000601b8000: C:\Program Files\Mozilla Firefox\components\browserdirprovider.dll
(00000000601c0000 - 00000000601e3000: C:\Program Files\Mozilla Firefox\components\brwsrcmp.dll
(0000000060210000 - 0000000060273000: C:\Program Files\Mozilla Firefox\sqlite3.dll
(0000000060340000 - 00000000603ea000: C:\Program Files\Mozilla Firefox\nss3.dll
(00000000603f0000 - 0000000060404000: C:\Program Files\Mozilla Firefox\nssutil3.dll
(0000000060410000 - 0000000060430000: C:\Program Files\Mozilla Firefox\ssl3.dll
(0000000060430000 - 0000000060448000: C:\Program Files\Mozilla Firefox\smime3.dll
(0000000060490000 - 0000000060de7000: C:\Program Files\Mozilla Firefox\xul.dll
(0000000060df0000 - 0000000060df7000: C:\Program Files\Mozilla Firefox\xpcom.dll
(00000000662b0000 - 0000000066308000: C:\WINDOWS\system32\hnetcfg.dll
(0000000066d00000 - 0000000066d4e000: C:\Program Files\Mozilla Firefox\components\coFFPlgn.dll
(0000000066ff0000 - 000000006706c000: C:\Program Files\Common Files\Symantec Shared\coShared\CIM\2.6\IVPlugin.dll
(0000000067530000 - 0000000067561000: C:\Program Files\Common Files\Symantec Shared\coShared\CIM\2.6\coParse.dll
(000000006b0a0000 - 000000006b0c8000: C:\Program Files\Common Files\Symantec Shared\ccIPC.dll
(000000006b170000 - 000000006b20a000: C:\Program Files\Common Files\Symantec Shared\ccL70U.dll
(000000006bc30000 - 000000006bc51000: C:\Program Files\Common Files\Symantec Shared\ccVrTrst.dll
(000000006fb60000 - 000000006fba7000: C:\Program Files\Common Files\Symantec Shared\AppCore\AppMgr32.dll
(000000006fc10000 - 000000006fc20000: C:\Program Files\Common Files\Symantec Shared\AppCore\AppSet32.dll
(0000000071a50000 - 0000000071a8f000: C:\WINDOWS\system32\mswsock.dll
(0000000071a90000 - 0000000071a98000: C:\WINDOWS\System32\wshtcpip.dll
(0000000071aa0000 - 0000000071aa8000: C:\WINDOWS\system32\WS2HELP.dll
(0000000071ab0000 - 0000000071ac7000: C:\WINDOWS\system32\WS2_32.dll
(0000000071ad0000 - 0000000071ad9000: C:\WINDOWS\system32\WSOCK32.dll
(0000000072d10000 - 0000000072d18000: C:\WINDOWS\system32\msacm32.drv
(0000000072d20000 - 0000000072d29000: C:\WINDOWS\system32\wdmaud.drv
(0000000073000000 - 0000000073026000: C:\WINDOWS\system32\WINSPOOL.DRV
(0000000074720000 - 000000007476b000: C:\WINDOWS\system32\MSCTF.dll
(0000000074d90000 - 0000000074dfb000: C:\WINDOWS\system32\USP10.dll
(00000000754d0000 - 0000000075550000: C:\WINDOWS\system32\CRYPTUI.dll
(00000000755c0000 - 00000000755ee000: C:\WINDOWS\system32\msctfime.ime
(0000000075cf0000 - 0000000075d81000: C:\WINDOWS\System32\mlang.dll
(0000000076380000 - 0000000076385000: C:\WINDOWS\system32\MSIMG32.dll
(0000000076390000 - 00000000763ad000: C:\WINDOWS\system32\IMM32.dll
(00000000763b0000 - 00000000763f9000: C:\WINDOWS\system32\COMDLG32.dll
(00000000767f0000 - 0000000076817000: C:\WINDOWS\system32\schannel.dll
(00000000769c0000 - 0000000076a73000: C:\WINDOWS\system32\USERENV.dll
(0000000076b40000 - 0000000076b6d000: C:\WINDOWS\system32\WINMM.dll
(0000000076c30000 - 0000000076c5e000: C:\WINDOWS\system32\WinTrust.dll
(0000000076c90000 - 0000000076cb8000: C:\WINDOWS\system32\IMAGEHLP.dll
(0000000076d60000 - 0000000076d79000: C:\WINDOWS\system32\iphlpapi.dll
(0000000076f20000 - 0000000076f47000: C:\WINDOWS\system32\DNSAPI.dll
(0000000076f60000 - 0000000076f8c000: C:\WINDOWS\system32\WLDAP32.dll
(0000000076fb0000 - 0000000076fb8000: C:\WINDOWS\System32\winrnr.dll
(0000000076fc0000 - 0000000076fc6000: C:\WINDOWS\system32\rasadhlp.dll
(0000000076fd0000 - 000000007704f000: C:\WINDOWS\system32\CLBCATQ.DLL
(0000000077050000 - 0000000077115000: C:\WINDOWS\system32\COMRes.dll
(0000000077120000 - 00000000771ab000: C:\WINDOWS\system32\OLEAUT32.dll
(0000000077270000 - 0000000077296000: C:\WINDOWS\system32\IESetting.dll
(00000000773d0000 - 00000000774d3000: C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2982_x-ww_ac3f9c03\COMCTL32.dll
(00000000774e0000 - 000000007761d000: C:\WINDOWS\system32\ole32.dll
(0000000077760000 - 00000000778d0000: C:\WINDOWS\system32\shdocvw.dll
(0000000077920000 - 0000000077a13000: C:\WINDOWS\system32\SETUPAPI.dll
(0000000077a80000 - 0000000077b14000: C:\WINDOWS\system32\CRYPT32.dll
(0000000077b20000 - 0000000077b32000: C:\WINDOWS\system32\MSASN1.dll
(0000000077bd0000 - 0000000077bd7000: C:\WINDOWS\system32\midimap.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 - 0000000077f01000: C:\WINDOWS\system32\RPCRT4.dll
(0000000077f10000 - 0000000077f57000: C:\WINDOWS\system32\GDI32.dll
(0000000077f60000 - 0000000077fd6000: C:\WINDOWS\system32\SHLWAPI.dll
(0000000077fe0000 - 0000000077ff1000: C:\WINDOWS\system32\Secur32.dll
(0000000078050000 - 0000000078120000: C:\WINDOWS\system32\WININET.dll
(0000000078130000 - 00000000781cb000: C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.1433_x-ww_5cf844d2\MSVCR80.dll
(000000007c420000 - 000000007c4a7000: C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.1433_x-ww_5cf844d2\MSVCP80.dll
(000000007c630000 - 000000007c64b000: C:\WINDOWS\WinSxS\x86_Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_cbb27474\ATL80.DLL
(000000007c800000 - 000000007c8f5000: C:\WINDOWS\system32\kernel32.dll
(000000007c900000 - 000000007c9b0000: C:\WINDOWS\system32\ntdll.dll
(000000007c9c0000 - 000000007d1d7000: C:\WINDOWS\system32\SHELL32.dll
(000000007e410000 - 000000007e4a0000: C:\WINDOWS\system32\USER32.dll
(000000007f560000 - 000000007f68e000: C:\WINDOWS\system32\urlmon.dll
*----> State Dump for Thread Id 0xcb8 <----*
eax=7ffdd000 ebx=0012fb24 ecx=0000001c edx=7c90eb94 esi=00000000 edi=7ffde000
eip=7c90eb94 esp=0012fafc ebp=0012fb98 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\ntdll.dll -
function: ntdll!KiFastSystemCallRet
7c90eb89 90 nop
7c90eb8a 90 nop
ntdll!KiFastSystemCall:
7c90eb8b 8bd4 mov edx,esp
7c90eb8d 0f34 sysenter
7c90eb8f 90 nop
7c90eb90 90 nop
7c90eb91 90 nop
7c90eb92 90 nop
7c90eb93 90 nop
FAULT ->ntdll!KiFastSystemCallRet:
7c90eb94 c3 ret
7c90eb95 8da42400000000 lea esp,[esp]
7c90eb9c 8d642400 lea esp,[esp]
7c90eba0 90 nop
7c90eba1 90 nop
7c90eba2 90 nop
7c90eba3 90 nop
7c90eba4 90 nop
ntdll!KiIntSystemCall:
7c90eba5 8d542408 lea edx,[esp+0x8]
7c90eba9 cd2e int 2e
*----> Stack Back Trace <----*
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\USER32.dll -
WARNING: Stack unwind information not available. Following frames may be wrong.
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\ole32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Program Files\Common Files\Symantec Shared\AppCore\AppMgr32.dll -
ChildEBP RetAddr Args to Child
0012fb98 7e4195f9 00000002 0012fbc0 00000000 ntdll!KiFastSystemCallRet
0012fbf4 77512235 00000001 0012fcdc ffffffff USER32!GetLastInputInfo+0x105
0012fc1c 77557227 0012fcdc ffffffff 0012fc48 ole32!CoUnmarshalInterface+0x13e2
0012fc90 7756500a 00000002 ffffffff 00000001 ole32!CoWaitForMultipleHandles+0xe6
0012fce4 6fb62ad2 77606908 00000100 6fb9f8c0 ole32!CoWaitForMultipleHandles+0xdec9
0012fd00 6fb705c5 3744abe4 6fba0068 00c47004 AppMgr32+0x2ad2
0012fd28 6fb87338 00000001 00000000 6fb60000 AppMgr32!DllCanUnloadNow+0x7e38
00c46fc8 d20aa549 d20a7a0b d20a79fd d20a79e7 AppMgr32+0x27338
d20aa519 00000000 00000000 00000000 00000000 0xd20aa549
I am not sure what that all means...there was more but it wouldnt let me post it all.