Welcome to WebmasterWorld Guest from

Forum Moderators: bill

Message Too Old, No Replies

"hungapp" message.and crash

Has anyone else successfully identified the cause?



5:57 pm on Sep 13, 2005 (gmt 0)

10+ Year Member


I'll preface this by saying that I am already a regular user and lover of Firefox. No need to move this thread in the direction of "why not to use Internet Explorer 6.0", k? :)

Starting in just the past few weeks....when I use Internet Explorer (IE)...(and I have installed up through service pack 2)....when clicking on links (no set pattern...some through Yahoo email, some on websites, etc.).....

...about 50% of the time IE freezes up...and I have to use the Windows Task Manager to close it.

A review of the Windows "event viewer" shows that the error is always the same "hung app".

I already had AdAware and AdWatch installed...and they always have run each night...along with Microsoft Spyware scans...and along with PC-cillin nightly scans....and both before and after this problem started on IE....nothing has ever come up on any of the scans I run each day that would indicate that "malware" was a problem. For now, please assume that my system is clean, k?

I have a slight suspicion that the Yahoo toolbar (version 6.0) that I installed via the Yahoo Messenger (version 7.0) installation might have something to do with it....but I'm not nearly convinced of that. I have always used Yahoo Toolbar in the past...like it for the direct "save to MyWeb" feature....and have never had a problem....for a long time.

So...have any of you dealt with...and identified the cause of....the "hungapp" problem?


7:01 pm on Sep 13, 2005 (gmt 0)

10+ Year Member

The "Hung Application" message is probably generated because of the way you killed the application -- like the ring around a glass is a sign of drinking soluble aspirin, not a sign of a headache.

Assuming that you're technically competent to do so, I'd recommend using a combination of TCPView, FileMon, RegMon and ProcessExplorer from [sysinternals.com...] to investigate the state of the application when the hang occurs. With a bit of luck you'll trace it back to specific file or network activity, or find the thread that's either hung up or is chewing CPU.

[sysinternals.com...] gives an example of using the tools to solve a similar problem.


7:42 pm on Sep 13, 2005 (gmt 0)

10+ Year Member


Thank you so very much. Please know that your quick response...instructive advice...and the immensely relevant links...made me so wonderfully happy to see.

Rock on!


Featured Threads

Hot Threads This Week

Hot Threads This Month