Thread lifecycle on ThreadDeath

Question

I wanted to start a computation and terminate it on user Cancel. You say that calling Thead.stop() unlocks all monitors and raises ThreadDeath exception. This means that finally is still called.

Suppose I do not care about the locks but want to release the resources allocated so far. I would like the canceller to know/wait until thread has finished released its allocations. Suppose the finally section has an infinite loop in the finally section. Will thread.join succeed to that thread?

score 1 · Accepted Answer · answered May 12 '16 at 20:10

1

It depends on what code the thread is executing at the point where ThreadDeath is thrown. For instance, if your thread is stopped just as it happens to reach the top of a finally block, then you could have a situation where ThreadDeath is thrown after the block is entered but before the resource is closed, and that finally block would not be completed.

It would be a lot less error-prone to use interruption, which lets the thread being interrupted have full control over how it finishes up and closes its resources.

answered May 12 '16 at 20:10

Nathan Hughes

94,330
19
181
276

AFAIK, you can interrupt only waiting threads, not ones that do computation in the heat. – Little Alien May 13 '16 at 06:24
@LittleAlien: yes, the thread being interrupted has to either check its interrupted flag or sleep or wait. – Nathan Hughes May 13 '16 at 12:37
@LittleAlien: to clarify i'm just saying this edge case exists where you may not have total certainty in all cases. – Nathan Hughes May 17 '16 at 15:46

Thread lifecycle on ThreadDeath

1 Answers1

Linked