User Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.1) Gecko/20120208 Firefox/10.0.1 SeaMonkey/2.7.1 Build ID: 20120208224119 Steps to reproduce: - Goto page http://www.mtv3.fi Seamonkey works fine - Hibernate WinXP - Start computer - Start Seamonkey - Goto page http://www.mtv3.fi Actual results: Seamonkey stops responding. Task Manager can not kill the Seamonkey process, must boot computer to continue. Installed plug-ins: Silverlight Plug-In 5.0.61118.0 Shockwave Flash 22.214.171.124 Java(TM) Platform SE 6 U30 6.0.300.12
Closing Seamonkey and all other open applications before the hibernation did not help.
>Task Manager can not kill the Seamonkey process That is a sign that Seamonkey hangs in some kernel code, probably a firewall or graphic card driver. You should get the same result with Firefox. Do you use a third party Firewall ? Does it work if you launch Seamonkey in the Safemode ? (holding the shift key while clicking on the Seamonkey Icon)
Disabling Comodo firewall or Safemode in Seamonkey did not help. But disabling Shockwave Flash plugin helps. Something wrong with that plugin?
Can you reproduce with Firefox (and same plugin(s))?
No, I can't reproduce this with Firefox and plugins, it works right. Graphic card drivers updated, but it did not help. More info about the Seamonkey Flash plugin: If the plugin is disabled, Seamonkey did not freeze and I can close it. But it still can be seen on Task Manager. And the process can not be removed. And a new instance of Seamonkey did not start, it only says that Seamonkey is already running.
Does hanged SeaMonkey process itself, or plugin-container process? If second, you can try to disable it and see if problem still there. To do this, follow Disabling crash protection steps from http://kb.mozillazine.org/Plugin-container_and_out-of-process_plugins
SeaMonkey process hangs, plugin-container is already disabled.
In first comment you mention, that even if you close SeaMonkey before hibernation, after resuming it doesn't work, is that right? How exactly it not working - not starting or in some other way? Also, can you try, if problem exists with latest nightly from - http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-comm-central-trunk/seamonkey-2.11a1.en-US.win32.zip Just unpack it in separate directory, close current version and run new one
1. I downloaded nightly build. 2. Close Seamonkey. 3. Unpack zip-file to temp folder. 4. Start new version of Seamonkey. 5. Browse internet (about half an hour), works very fine. 6. Close Seamonkey (other programs are not started). 7. Hibernate WinXP. 8. Resume from hibernation. 9. Start new version of Seamonkey. 10. Browse internet, after couple of minutes, Seamonkey stops responding. 11. Start Task Manager and go to Applications tab. 12. Select Seamonkey task and push End Task button -> Seamonkey windows close. 13. Go to Processes tab of Task Manager, seamonkey.exe process is still there. 14. Select seamonkey.exe process and push End Process button -> Task Manager can not kill the seamonkey.exe process. 15. Try start new instance of Seamonkey -> Pop-up window says that Seamonkey is already running. 16. Shutdown WinXp -> Windows did not shutdown (I wait about 20 minutes). 17. Turn power OFF and ON, WinXP starts normally, and Seamonkey is working OK.
Download Process Explorer from http://technet.microsoft.com/en-us/sysinternals/bb896653, start it after resuming from hibernation, but before SeaMonkey start, after SeaMonkey hangs, open it properties in Process Explorer, go to Threads tab and look, what thread is on top. Also, select it, click on Stack button and copy data from there too
After crash: Top thread NPSWF32.dll+0x1cd33c Stack ntdll.dll+0xe514 kernel32.dll+0x2542 NPSWF32.dll+0x1cd1d0 NPSWF32.dll+0x1cd309
If you reenable plugin-container, situation stay the same?
Resolved per whiteboard, feel free to reopen if you still experiencing problem and provide crash ids from about:crashes
Status: UNCONFIRMED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INCOMPLETE
Whiteboard: closeme INCO 2012-07-01
You need to log in before you can comment on or make changes to this bug.