[Mono-dev] Thread Pool WAPI Ref Problems
pat.earl at advmeas.com
Mon Sep 25 12:12:50 EDT 2006
Putting one unpleasant hack in the source eliminated the leaking wapi
thread handles in the test application I was using. However, when
running the same code on the production server, there are still many
thread handles leaking from other places. It seems there is some
systematic problem with leaking handles. Is it possible that a solution
might be created that takes care of the wapi handles in a more automatic
manner? Perhaps certain handles could be freed automatically if a flag
is set on creation.
Along the same lines, could somebody explain what the relationship is
between threads created by mono_thread_create and the garbage
collector? What happens to those MonoThread objects? Where are those
handles meant to be freed?
I saw a post that at some point there was the intention to move objects
away from the garbage collector and have them managed internally. Is
this still the intention?
I assume that if references to handles can escape from the internal code
to the managed space, we must then allow the gc to deal with closing
those handles. Is that correct?
Thanks for the clarification on this.
More information about the Mono-devel-list