[GHC] #3273: memory leak due to optimisation

[GHC]

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

 Replying to [comment:3 simonmar]:

 After examining a core dump I am now pretty sure that the leak is caused
 by the full-laziness optimization and the original program could benefit
 from a mechanism to selectively disable it like mentioned by simonpj in
 that other ticket.

 The behaviour of the condensed program is still a bit weird because it is
 unclear (to me at least) why removing an 'id' call affects the full
 laziness optimization in this example. However, section 4.9.2 of the GHC
 user guide says explicitly that "GHC doesn't consistently apply full-
 laziness" so it may be fine to apply it if all 'id's are there and not if
 one is missing.

 If so, then there is nothing to fix.

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