Better stack management please
(From Adrian Hey)
The current ghc rts stack management has a number of undesirable properties, at least as far as I understand it. The current implementation is explained in this post:
http://haskell.org/pipermail/glasgow-haskell-users/2007-May/012472.html
But it's worse than that. What the above post doesn't explain is that if the stack temporarily "blows up" due to deep recursion, the memory claimed from the heap for that threads stack will never be released, at least according to this post:
http://www.haskell.org/pipermail/haskell-cafe/2008-February/039010.html
There have been a number of threads discussing this, all of which contain too much information and too many points of view to reproduce in this ticket, so here are some relevant starting points:
http://haskell.org/pipermail/glasgow-haskell-users/2007-May/012467.html http://www.haskell.org/pipermail/haskell-cafe/2008-January/038790.html
What I would like is summarised here:
http://www.haskell.org/pipermail/haskell-cafe/2008-February/039115.html
Trac metadata
| Trac field | Value |
|---|---|
| Version | 6.8.2 |
| Type | FeatureRequest |
| TypeOfFailure | OtherFailure |
| Priority | normal |
| Resolution | Unresolved |
| Component | Runtime System |
| Test case | |
| Differential revisions | |
| BlockedBy | |
| Related | |
| Blocking | |
| CC | |
| Operating system | Unknown |
| Architecture | Unknown |