#8124: Possible leaks when using foreign export. --------------------------------------------+------------------------------ Reporter: augustss | Owner: simonmar Type: bug | Status: new Priority: highest | Milestone: 7.8.2 Component: Runtime System | Version: 7.6.3 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: Type of failure: Runtime performance bug | Unknown/Multiple Test Case: | Difficulty: Unknown Blocking: | Blocked By: | Related Tickets: --------------------------------------------+------------------------------ Changes (by simonmar): * owner: => simonmar * priority: normal => highest * milestone: => 7.8.2 Comment: Thinking about it a bit more, it ought to be possible to clean these up automatically. The tricky bit is knowing when to do so - too eager and we penalize threads that are doing frequent in-calls, too lazy and we have the memory leak again. Perhaps just sweeping the table during a major GC would be good enough. Better might be to only free Tasks that have survived one major GC cycle without being used, but that's a bit more work. I'll look into this when I've got some time. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/8124#comment:6 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler