[GHC] #3273: memory leak due to optimisation

[GHC]

#3273: memory leak due to optimisation
-----------------------------------------+----------------------------------
    Reporter:  sebf                      |        Owner:                  
        Type:  run-time performance bug  |       Status:  closed          
    Priority:  normal                    |    Milestone:  6.12 branch     
   Component:  Compiler                  |      Version:  6.10.1          
    Severity:  normal                    |   Resolution:  duplicate       
    Keywords:                            |   Difficulty:  Unknown         
    Testcase:                            |           Os:  Unknown/Multiple
Architecture:  Unknown/Multiple          |  
-----------------------------------------+----------------------------------
Changes (by simonpj):

  * status:  new => closed
  * resolution:  => duplicate

Comment:

 OK, so the conclusion seems to be that, while this case is more
 interesting than #917, it is simply a manifestation of the full laziness
 space leak.  And alas we don't know a good way to get the benefits of full
 laziness (sharing computation) without occasionally paying its costs (in
 terms of space).

 I'm going to close this one as a duplicate, and cross-link from #917.

 Simon

-- 
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/3273#comment:6>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler