[GHC] #10812: High memory usage after performing GC

GHC ghc-devs at haskell.org
Fri Dec 2 16:41:27 UTC 2016


#10812: High memory usage after performing GC
---------------------------------+--------------------------------------
        Reporter:  danilo2       |                Owner:
            Type:  bug           |               Status:  new
        Priority:  high          |            Milestone:
       Component:  Compiler      |              Version:  7.10.2
      Resolution:                |             Keywords:
Operating System:  MacOS X       |         Architecture:  x86_64 (amd64)
 Type of failure:  None/Unknown  |            Test Case:
      Blocked By:                |             Blocking:
 Related Tickets:                |  Differential Rev(s):
       Wiki Page:                |
---------------------------------+--------------------------------------

Comment (by simonmar):

 Firstly I think the huge list is being lifted out and shared between the
 two computations, which accounts for all the memory still live at the end
 of "A".  Also, after all the weak pointers have died, it takes a little
 while for all the finalizers to complete, so the memory won't be free at
 the point where we do the `performGC`.  If you compile with `-threaded`
 you'll get an idle GC during the waiting period which will release some
 memory.

 Overall I haven't seen anything going wrong here.

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


More information about the ghc-tickets mailing list