#2638: runInteractiveCommand on Win32 leaks, produces inconsistent behavior
-------------------------------+--------------------------------------------
Reporter: sclv | Owner:
Type: bug | Status: new
Priority: normal | Milestone: 6.10.1
Component: libraries/process | Version: 6.8.3
Severity: normal | Resolution:
Keywords: | Difficulty: Unknown
Testcase: | Architecture: vax
Os: Windows |
-------------------------------+--------------------------------------------
Changes (by simonmar):
* milestone: => 6.10.1
Comment:
Yes, we use job objects in the testsuite to ensure that when a test runs
out of time we can kill it and all of its children. Ian did the necessary
hackery, here:
* [http://darcs.haskell.org/testsuite/timeout/WinCBindings.hsc]
* [http://darcs.haskell.org/testsuite/timeout/timeout.hs]
but as you say, I don't think this helps us with `terminateProcess`. We
have no justification for creating a new job object for
`runInteractiveCommand`, the parent process might well prefer it if we
didn't (e.g. it would probably screw up the testsuite's use of job
objects).
BTW, I've verified the memory leak in the original bug report.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/2638#comment:3>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
