On 2015-05-25 06:52, Eric Voskuil wrote: > I’ve seen memory consumption rise almost linearly, which looks a lot
> like an infinite loop or recursion. Usually, on its own, this stops and
> sometimes restarts. So it feels like there is a feedback loop across
> threads that is terminating based on a race condition (so it can
> eventually clear itself). That’s some real speculation, but this is the
> best I have without better diagnostics. I've also seen once the
> process
> get terminated by the OS before it has a chance to recover.
Just curious, do you have any thoughts on *what* is taking this memory -
do you understand it to be blocks or transactions (of some sort), or
something else?
I guess it should not be stack space from a big recursion as that is
capped at ~4MB per thread.