[procps] Re: Bug in the forrest view
- From: Jaromir Capik <jcapik@xxxxxxxxxx>
- To: procps@xxxxxxxxxxxxx
- Date: Wed, 22 Oct 2014 07:38:33 -0400 (EDT)
> Hi Jaromir,
Hi Jim.
> Don’t invest any (more) effort researching stack size.
>
> The forest view SEGV was not caused by a stack overflow. There were just 143
> invocations and the named function could have called itself tens of
> thousands of times before exhausting the stack.
>
> I’m pretty sure I’ve got a handle on the real cause but I’m on the fence as
> to whether or not it should even be addressed. After all, we're dealing
> with a runaway fork loop in a vim plugin.
>
> Must top be that resilient? If so, could you tolerate some distortion in the
> forest view presentation?
I think it would be nice to use the 'top' tool for detection of such loops.
In this case it's absolutely ok to distort the forest view for example
by limiting the depth to some reasonable number (100 ?) and then appending
something like dummy entry with 3 dots.
Thank,
Jaromir.
Other related posts:
