https://bugzilla.novell.com/show_bug.cgi?id=474217
https://bugzilla.novell.com/show_bug.cgi?id=474217#c10 --- Comment #10 from Sven Groot <sgr...@tkl.iis.u-tokyo.ac.jp> 2010-12-14 14:45:27 UTC --- Lluis, thanks for your response. Your concern is not entirely invalid. Waiting on a thread pool thread from a thread pool thread is something that can always lead to deadlock, and should therefore never be done. However, in Microsoft .Net, remoting requests are also executed on the thread pool, so it has exactly the same issue. You cannot safely wait for a thread pool thread from a remoting call in Microsoft .Net, so I don't see why it would be a problem to use the same implementation in Mono. The current homegrown thread pool doesn't just have the PoolGrowDelay issue, it's also subject to a race condition, see bug #557212, which I filed long ago but no one ever responded to. I think using the system thread pool would be a better option. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ mono-bugs maillist - mono-bugs@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-bugs
