Hello everyone,
I've been running into the following error:
Reproduction.exe: getMBlocks: VirtualAlloc MEM_RESERVE 1 blocks
failed: Not enough storage is available to process this command.
The confusing part to me is that when the error occurs, Task Manager
reports that the process is
Rich Fought wrote:
Did you try GHC's heap profiler?
Or simply running your program with +RTS -Sstderr will give you a clue
about the shape of the heap usage - each line is a single GC, and it
includes the amount of live data at that point.
If your program has a flat heap profile and yet is
Did you try GHC's heap profiler?
Or simply running your program with +RTS -Sstderr will give you a clue
about the shape of the heap usage - each line is a single GC, and it
includes the amount of live data at that point.
If your program has a flat heap profile and yet is still grabbing more
Simon Marlow wrote:
What tool(s) did you use to obtain this figure?
This particular figure was gathered using perfmon logs collecting once
per second from my application, while running in WinDbg to break on
getMBlocks(). The particular memory variables tracked are "Private
Bytes
hat
keeps repeating until memory runs out. WinDbg has revealed that this
stepping coincides with the GHC runtime function getMBlocks().
>
My question is: what conditions affect when the runtime determines that
it needs more memory? Is it a pure "no more room" trigger or is there
some s
that this
stepping coincides with the GHC runtime function getMBlocks().
My question is: what conditions affect when the runtime determines that
it needs more memory? Is it a pure "no more room" trigger or is there
some sort of algorithm behind it?
I assume that this behavior means I sti
