Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister
 
PerlMonks  

Re: perl dying without a trace

by cog (Parson)
on Oct 24, 2006 at 22:23 UTC ( [id://580415]=note: print w/replies, xml ) Need Help??


in reply to perl dying without a trace

I can't find a limited code sample that still displays this behaviour.

Sure you can... it's your whole code! :-)

Seriously, now; start removing line by line until it stops failing the way it does (but not failing in a different way; simply running and not doing anything will do the trick).

Not with 100% certainty, but I'm rather sure you'll manage to decrease the quantity of code that produces that behaviour :-)

Replies are listed 'Best First'.
Re^2: perl dying without a trace
by Crackers2 (Parson) on Oct 24, 2006 at 23:03 UTC

    The problem is that it only happens about 10 minutes into the run.

    The main loop of the program is something like this:

    while (not_done_yet) { if (queue not full) { add new element to queue } @new_queue = (); foreach $element (@queue) { if (state==1) { blah blah; state=2 } ... if (timed_out) { next; } push $element, @new_queue; } @queue = @new_queue; }

    The issue does not show up if I decrease the queue size from the normal 50 to 5, or the timeout from the default 600 seconds to 30. It shows up after the queue has completely filled up (takes a few minutes), and the first few elements have timed out.

    I'll see what I can do to decrease it, but I'm not hopeful.

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://580415]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others drinking their drinks and smoking their pipes about the Monastery: (1)
As of 2024-04-19 00:14 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found