On 02.11.2010, at 10:20, Simon Marlow wrote:
It's not really a question of priority, rather that we don't know of
a good way to fix it!
I would not have guessed that there exists a Haskell related problem
that cannot immediately be fixed by the ghc headquarters ; )
If I understand correc
I finally got some spare time to do some GHC hacking, and after feeling my
way around http://hackage.haskell.org/trac/ghc/ticket/4262 I came up with the
following patch, which appears to work (that is, bound the number of worker
threads hanging around after FFI calls):
diff -rN -u old-ghc-clean/rt
