How Do I Kill A Thread In Onclose() Event At Close(X)

Question

0.00/5 (No votes)

See more:

MFC

how do i kill a thread in Onclose() event at CLOSE(X)

Posted 31-Aug-15 1:23am

TusharZoo

Add a Solution

Comments

Sergey Alexandrovich Kryukov 31-Aug-15 11:12am

First of all, why? Yes, sometimes it is needed... but this is a complicated issue.
—SA

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2015-08-31T05:24:00

This is a painful and complicated issue, which triggers heated discussions from time to time. Many would tell you that you should never terminate thread; and a thread should gracefully terminate itself (just exit), after some polling of some flag (in shared data) which would give the thread an order to exit. But I rather say "never say 'never'"; unfortunately, there are whole big fields of engineering where such things are totally infeasible. I would say more: authors of OS purely recognize existence of such fields.

Please see my past answer:
Close correcly the thread inside a dll[^].

Even if you won't use it, it will give you the idea on how serious this seemingly simple topic is.

As I don't know your application, I can first advise the cooperative termination described in first paragraph. If it cannot work for you, I can even mention really dirty thing: a call to TerminateThread. Yes, it is dirty and strongly discouraged, but if the design of your thread does not allow simple cooperative termination you have one more excuse: if this is the last thing your application does, you won't have to deal with the possibly bad consequences of this call.

—SA

P.S.: It is very likely that this post will be down-voted. I would advise you to not pay attention for that. This topic is generally poorly understood.