I have a fairly simple applet that does use some fairly complex,
multi-threaded code. The problem is that when the page where the
applet resides is reloaded, it sometimes hangs the entire browser.
I've tracked this down to the point of knowing that a ThreadDeath
Error is being thrown. Here is the stack trace:
I have a couple questions:
1. Given that Sun deprecated Thread.stop() ages ago, why are Sun
themselves calling the stop method?
2. According to the debugging I've been able to do, this ThreadDeath
error is being thrown ON A NEWLY CREATED thread AFTER the applet has
already completely reloaded and is actually running. This whole
process of shutting down the applet and then reloading it takes less
than two seconds. I'm just reloading the page. The breakdown is: The
applet is stopped via stop(), then destroyed via destroy(). My
threads are shut down. The page reloads, and the applet reloads,
running its init() and start() methods. The applet starts running and
then *boom*, maybe 20% of the time it gets a ThreadDeath error. This
makes no sense to me. The threads from the previous incarnation of
the applet HAVE been cleaned up and have gone away. So why does JVM
send this ThreadDeath Error? And why send it to my newly created
thread which was running along perfectly fine?
Catching and discarding the ThreadDeath error is not an option.
You're not supposed to do that, and besides, I tried and it doesn't
Any thoughts? Thanks.
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
Visit the Apple Store online or at retail locations.
Copyright © 2011 Apple Inc. All rights reserved.