current_commit stat negative

[maxbachmann]

current_commit stat negative

[daanx]

That looks like spam? -- I would not click on that link. Let me see if I can remove it..
(as an aside, I think the commit can be negative due to thread interaction but let me think about this a bit more and reply in more detail)

[maxbachmann]

From my understanding current_commit should match the amount of memory committed in prim.c. If I add my own atomic to track the calls in there the numbers match for a while and start to go out of sync once threads get destroyed.

These two numbers match for a while and then appear to go out of sync once threads start to get destroyed. At this point current_commit appears to get decreased by 32mb without any corresponding decommit in prim.c.