Finally hunted down the Parallel deadlock. Packets were being handled asynchronously (filling up the threadpool with handlers), which would turn around and try to do parallel operations on the starved threadpool. The solution for now is to disable Parallel.cs operations until we can gracefully handle parallel operations with a potentially starved threadpool

This commit is contained in:
John Hurliman
2009-10-27 02:36:57 -07:00
parent b498693cff
commit 3a1ee79ee4
2 changed files with 10 additions and 7 deletions

View File

@@ -49,7 +49,7 @@
; in parallel. Running in parallel should increase performance
; on a multi-core system, but will make debugging more
; difficult if something deadlocks or times out
use_async_when_possible = true
use_async_when_possible = false
; Max threads to allocate on the FireAndForget thread pool
; when running with the SmartThreadPool option above