Re: Thread mysteriously terminates.
From: Sean Wolfe (noemail_at_please.com)
Date: 02/27/04
- Next message: Jerry III: "Re: Thread mysteriously terminates."
- Previous message: Yogesh Shetty: "Re: Increase in Memory"
- In reply to: Sean Wolfe: "Thread mysteriously terminates."
- Next in thread: Jerry III: "Re: Thread mysteriously terminates."
- Reply: Jerry III: "Re: Thread mysteriously terminates."
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 26 Feb 2004 20:57:34 -0600
Some additional data on this issue. When the application that is feeding
into the "aggregator" class is throttled to about 1/4 of the load i
described, the issue doesn't happen, or happens less. It also seems to
happen on multi-proc HT emabled machines, and not single proc(I haven't
seen it at least). I haven't tried it on Multi-Proc NonHT machines or
Single Proc HT machines. That's my next step though.
I looked that the thread in systernals.com Process Explorer, and it
looks like the Thread somehow gets dereferenced under those higher
loads. When it looses the thread, the thread still appears in the list
of handles, but only has one reference. Most .NET threads has 3-4
references if not more. If i select properties for the Process, and then
view the Threads tab, the thread is no longer in the list (it does
appear when the thread is operating properly). So it would seem that the
thread has terminated or lost it's reference, but it's handle hasn't
been released. Did the GC maybe mistakenly collect this thread? that
would seem unusual since I'd see this thread object to appear as a Root
node in the GC Heap.
Also to note, I do have a method attached to the AppDomain's
UnhandledException event. So if there were any excpetions that slipped
through my class this should be able to catch it.
I also had put a Debug message just outside of the main while
threadloop, in case for some reason it had been able to exit out of
there for some reason. That expression is never called, so I know it's
not that the thread is somehow getting out of the loop.
This one is a puzzler!
Sean
- Next message: Jerry III: "Re: Thread mysteriously terminates."
- Previous message: Yogesh Shetty: "Re: Increase in Memory"
- In reply to: Sean Wolfe: "Thread mysteriously terminates."
- Next in thread: Jerry III: "Re: Thread mysteriously terminates."
- Reply: Jerry III: "Re: Thread mysteriously terminates."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|