in reply to how to localise a problem?
Hi,
that looks like something is accumulating over time. So I would look at objects, variables which are probably used more then once over the time. Probably they are not initialized properly on every run. Another guess is that you expect that a object is shutdown correctly while going out of scope but it doesn't. Check the manual of the "bigger" objects you use.
UPDATE: I just looked at the GraphViz2 (2.06) package. It seems that there is exactly one line where IPC::Run is used:
So, the dot_input is logged if logging is enabled. Probably the right point to catch the culprit.$self -> dot_input(join('', @{$self -> command -> print} ) . "}\n"); $self -> log(debug => $self -> dot_input); my($stdout, $stderr); IPC::Run::run([$driver, "-T$format"], \$self -> dot_input, \$stdout, \ +$stderr);
Best regards
McA
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: how to localise a problem?
by Dave Howorth (Scribe) on Nov 27, 2012 at 12:14 UTC | |
by McA (Priest) on Dec 04, 2012 at 21:12 UTC |