Bugzilla – Bug 317235
thread handles leak
Last modified: 2007-09-15 21:24:46 UTC
---- Reported by bmaurer@users.sf.net 2005-02-18 16:14:31 MST ---- The above assertion happens after a bit of time on: using System; using System.Threading; class X { static void Main () { Thread [] threads = new Thread [10]; while (true) { for (int i = 0; i < threads.Length; i ++) { threads [i] = new Thread (Worker); threads [i].Start (); } for (int i = 0; i < threads.Length; i ++) { threads [i].Abort (); } Console.Write ("."); } } static void Worker () { while (true) Thread.Sleep (10); } } ---- Additional Comments From gonzalo@ximian.com 2005-04-19 01:55:12 MST ---- Looks like the same problem: the shared handles file needs to grow. *** This bug has been marked as a duplicate of https://bugzilla.novell.com/show_bug.cgi?id=MONO71274 *** ---- Additional Comments From lupus@ximian.com 2005-04-19 11:22:20 MST ---- It looks like in this case the thread objects are not collected (either the runtime or the io-layer parts of it). Different bug than 71274. ---- Additional Comments From bmaurer@users.sf.net 2005-06-29 15:19:47 MST ---- Am only able to reproduce hangs here now. They come from adding an APC. This takes a lock, which is unsafe inside a signal handler. So am marking as a dup of https://bugzilla.novell.com/show_bug.cgi?id=MONO58065. *** This bug has been marked as a duplicate of https://bugzilla.novell.com/show_bug.cgi?id=MONO58065 *** Unknown operating system unknown. Setting to default OS "Other". This bug was marked DUPLICATE in the database it was moved from. Changing resolution to "MOVED"