Title: RE: Multiple perl.exe processes not going away
Any time the Perl doesn't terminate normally, it will stay running. I too had the problem that a certain (error) path through my code caused an infinite loop. Only hit it very occasionally, so very difficult to find, but examine all 'for' loops or other loops, or reentrant code.
 
Clicking STOP on the browser will not kill the perl process. IIS will not kill runaway processes, and like William says, you cannot kill it yourself... have to reboot.
 
Cheers,
Jonathan
"Joust Not with Dragons, for Thou art Crunchy, and Goode with Ketchup..."
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 15, 2000 12:46 PM
To: [EMAIL PROTECTED]
Subject: RE: Multiple perl.exe processes not going away

I've seen this happen, too. I don't think this'll help, but here's something anyway.

I wrote a CGI/Perl program continuously checked a certain directory for files.  It was initiated by clicking a submit button on a webpage I wrote. Once submit was clicked, it began continuously checking a directory for files.

However, even after I hit escape to stop the webpage, the Perl process kept running, so the ONLY way I could stop the process was to reboot the webserver. (This was on my NT workstation running PWS, so it wasn't a big deal.)

I wish I could tell you how to track it down. I never did figure it out.

Check for Perl scripts that run other Perl scripts.

DTH (Doubt This Helps),
-WM   <><

-----Original Message-----
From: Tim Callaghan [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 15, 2000 10:27 AM
To: [EMAIL PROTECTED]
Subject: Multiple perl.exe processes not going away


I've got a serious issue with our application.

At the end of any given day we have a number (10 or so) of perl.exe
processes that are consuming ~10MB memory and no cpu time on our web server.

We're running the latest Apache (1.3.14) and have seen this issue using
ActiveState 5.22 and 6.20.  We've also tested this (and have the same issue)
running Windows NT Server 4.0, Workstation 4.0, and Windows 2000
Professional.

If anyone can help me find the cause of this I would greatly appreciate it.

I've gone as far as to write a program that captures the process ID's of
running perl processes every 30 seconds, we're trying to track this back to
our apache access log to see if we can identify a CGI that is the culprit.

-Tim

_______________________________________________
Perl-Win32-Web mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/perl-win32-web

Reply via email to