Please do not reply to this email- if you want to comment on the bug, go to the URL shown below and enter your comments there.
Changed by [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=79060 --- shadow/79060 2006-09-21 18:35:28.000000000 -0400 +++ shadow/79060.tmp.29648 2006-09-22 12:13:08.000000000 -0400 @@ -261,6 +261,13 @@ Adding an explicit CloseHandle(thread->handle) call right after thread_cleanup in the start_wrapper function stopped those particularly nasty thread pool leaks for me. Since start_wrapper also seems to be used for garbage collected threads, perhaps this is not the best solution. Maybe there needs to be a flag in start_info that indicates if a thread should manually free its handle or not. + +------- Additional Comments From [EMAIL PROTECTED] 2006-09-22 12:13 ------- +Although the above CloseHandle eliminates the problem in the provided +test, running XSP and doing mostly boring ASP.NET type things still +leaks handles all over the place. It's leaking handles more slowly, +but still leaking them. Is there some way that the wapi handles can +be automatically freed when they're no longer needed? _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
