The thread '<No Name>' (0xedc) has exited with code 0 (0x0)

[Charlie Brown]

The thread '<No Name>' (0xedc) has exited with code 0 (0x0)

While debugging appplications, I often see this message popup in the VS
output window. Although I havent specifically written any
multithreading into my app, I would guess this means there is some
somewhere.

Can anyone offer some insight into this message?

 

[Michael Nemtsev]

Hello Charlie,

it means that you exit from you app normally and main thread was closed
<No Name> is the name of thread, that was not set.
IF you create new thread and set Thread.Name property you could see the
"The thread 'youName' has exited with code 0 (0x0)

CB> The thread '<No Name>' (0xedc) has exited with code 0 (0x0)
CB>
CB> While debugging appplications, I often see this message popup in the
CB> VS output window. Although I havent specifically written any
CB> multithreading into my app, I would guess this means there is some
CB> somewhere.
CB>
CB> Can anyone offer some insight into this message?
CB>
---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsch

 

[Ryan Liu]

I guess each form use an thread. And also the form trigger more threads when
it init components asynchronously. -Ryan

 

[Benny S. Tordrup]

Michael,

Youre not right. I've seen this message several times in a running
application that was not exiting at the time, the message occured. It comes
periodically.

Benny

 

[Charlie Brown]

Benny,
I have also seen this popup while my application has been idle. Maybe
6 or 7 entries over 10 minutes with no user activity.