Ticket #743 (closed bug: fixed)

Opened 7 years ago

Last modified 6 years ago

-M limit exceeded by a factor of 2

Reported by: simonmar Owned by: simonmar
Priority: normal Milestone: 6.6.1
Component: Runtime System Version: 6.4.1
Keywords: Cc: ketil+haskell@…
Operating System: Linux Architecture: x86
Type of failure: Difficulty: Unknown
Test Case: N/A Blocked By:
Blocking: Related Tickets:

Change History

Changed 7 years ago by guest

Just thought I'd mention that I get the same result when setting the limit using C hooks (RtsFlags?.GcFlags?.maxHeapSize) --k

Changed 7 years ago by simonpj

  • owner set to simonmar

Changed 7 years ago by igloo

  • testcase set to N/A
  • milestone changed from 6.6 to 6.6.1

Changed 6 years ago by simonmar

Further notes on this one: I can't reproduce the problem with the submitter's test case. It appears to be something system-dependent; Ketil can still reproduce it. Looking at a log of one of the offending runs, it seems the heap size levels off at the -M limit as expected, but the top output shows the process still growing.

I'm following up with Ketil to find out who/what is allocating the extra memory.

Changed 6 years ago by ketil@…

  • status changed from new to closed
  • resolution set to fixed

I've finally gotten around to build ghc 6.6 with the recent patch for this problem, and it appears the problem has been fixed. My program (rbr) now stick within the specified heap, until it OOMs (as expected). Thanks!

-k

Note: See TracTickets for help on using tickets.