EXP Systems Forum: Several capture.exe processes

Message

   Hello!

Somehow we've got too many capture.exe processes that hang in the memory. They do nothing. We use PDFRedirect (2.1.911) to print approx. 1000-3000 files per day on ~380 batch printers. Here is a shot from pslist:

PsList 1.22 - Process Information Lister
Copyright (C) 1999-2002 Mark Russinovich
Sysinternals - www.sysinternals.com

Name         Pid Pri Thd  Hnd    Mem     User Time   Kernel Time   Elapsed Time
Capture     6656   8   1   71    624   0:00:07.609   0:00:01.453   50:24:03.537
Capture     4352   8   1   71    616   0:00:07.812   0:00:01.656   50:20:04.555
Capture     3936   8   1   71    620   0:00:07.734   0:00:01.312   49:55:20.212
Capture     6888   8   1   71    644   0:00:07.328   0:00:01.406   49:02:43.018
Capture     7748   8   1   71    616   0:00:07.531   0:00:01.500   48:49:24.357
Capture     7796   8   1   71    644   0:00:07.453   0:00:01.625   48:39:47.411
Capture     4328   8   1   71    608   0:00:07.421   0:00:01.296   47:00:11.250
Capture     7716   8   1   71    644   0:00:05.953   0:00:01.015   46:00:17.265
Capture     7028   8   1   71    628   0:00:04.171   0:00:00.750   32:19:53.149
Capture     4300   8   1   71    628   0:00:03.609   0:00:00.734   32:10:09.785
Capture     6352   8   1   69    640   0:00:02.984   0:00:00.500   27:58:48.606
Capture     6160   8   1   69    640   0:00:02.953   0:00:00.578   27:49:11.492
Capture     7364   8   1   69    636   0:00:03.015   0:00:00.625   27:32:18.230
Capture     7332   8   1   69    652   0:00:02.953   0:00:00.671   27:28:33.516
Capture     4336   8   1   69    636   0:00:02.656   0:00:00.671   26:43:01.193
Capture     6128   8   1   69    632   0:00:03.187   0:00:00.609   26:10:16.153
Capture     7380   8   1   69    632   0:00:02.609   0:00:00.656   25:14:08.429
Capture     6944   8   1   69    640   0:00:03.046   0:00:00.640   25:09:12.265
Capture     5376   8   1   69    636   0:00:03.390   0:00:00.703   25:02:45.179
Capture     7740   8   1   69    636   0:00:03.015   0:00:00.453   24:58:13.015
Capture     7156   8   1   69    640   0:00:02.843   0:00:00.531   24:48:33.028
Capture     7820   8   1   69    664   0:00:02.593   0:00:00.515   24:29:11.019
Capture     1036   8   1   69    636   0:00:02.312   0:00:00.546   23:53:33.217
Capture     6712   8   1   69    600   0:00:02.375   0:00:00.546   23:44:07.696
Capture     5576   8   1   69    612   0:00:01.375   0:00:00.390   22:40:10.723
Capture     6264   8   1   69    664   0:00:01.500   0:00:00.437   22:29:07.611
Capture     3876   8   1   71    608   0:00:00.859   0:00:00.250    8:32:29.231
Capture     4988   8   1   71    628   0:00:01.000   0:00:00.328    8:09:15.555
Capture     4220   8   1   71    604   0:00:01.031   0:00:00.375    7:44:15.052

Why don't they close for hours?

Author	Message
lovetski Newbie Joined: 18 Apr 06 Location: Russian Federation Posts: 30	Topic: Several capture.exe processes Posted: 30 May 07 at 11:56AM
	Hello! Somehow we've got too many capture.exe processes that hang in the memory. They do nothing. We use PDFRedirect (2.1.911) to print approx. 1000-3000 files per day on ~380 batch printers. Here is a shot from pslist: PsList 1.22 - Process Information Lister Copyright (C) 1999-2002 Mark Russinovich Sysinternals - www.sysinternals.com Name Pid Pri Thd Hnd Mem User Time Kernel Time Elapsed Time Capture 6656 8 1 71 624 0:00:07.609 0:00:01.453 50:24:03.537 Capture 4352 8 1 71 616 0:00:07.812 0:00:01.656 50:20:04.555 Capture 3936 8 1 71 620 0:00:07.734 0:00:01.312 49:55:20.212 Capture 6888 8 1 71 644 0:00:07.328 0:00:01.406 49:02:43.018 Capture 7748 8 1 71 616 0:00:07.531 0:00:01.500 48:49:24.357 Capture 7796 8 1 71 644 0:00:07.453 0:00:01.625 48:39:47.411 Capture 4328 8 1 71 608 0:00:07.421 0:00:01.296 47:00:11.250 Capture 7716 8 1 71 644 0:00:05.953 0:00:01.015 46:00:17.265 Capture 7028 8 1 71 628 0:00:04.171 0:00:00.750 32:19:53.149 Capture 4300 8 1 71 628 0:00:03.609 0:00:00.734 32:10:09.785 Capture 6352 8 1 69 640 0:00:02.984 0:00:00.500 27:58:48.606 Capture 6160 8 1 69 640 0:00:02.953 0:00:00.578 27:49:11.492 Capture 7364 8 1 69 636 0:00:03.015 0:00:00.625 27:32:18.230 Capture 7332 8 1 69 652 0:00:02.953 0:00:00.671 27:28:33.516 Capture 4336 8 1 69 636 0:00:02.656 0:00:00.671 26:43:01.193 Capture 6128 8 1 69 632 0:00:03.187 0:00:00.609 26:10:16.153 Capture 7380 8 1 69 632 0:00:02.609 0:00:00.656 25:14:08.429 Capture 6944 8 1 69 640 0:00:03.046 0:00:00.640 25:09:12.265 Capture 5376 8 1 69 636 0:00:03.390 0:00:00.703 25:02:45.179 Capture 7740 8 1 69 636 0:00:03.015 0:00:00.453 24:58:13.015 Capture 7156 8 1 69 640 0:00:02.843 0:00:00.531 24:48:33.028 Capture 7820 8 1 69 664 0:00:02.593 0:00:00.515 24:29:11.019 Capture 1036 8 1 69 636 0:00:02.312 0:00:00.546 23:53:33.217 Capture 6712 8 1 69 600 0:00:02.375 0:00:00.546 23:44:07.696 Capture 5576 8 1 69 612 0:00:01.375 0:00:00.390 22:40:10.723 Capture 6264 8 1 69 664 0:00:01.500 0:00:00.437 22:29:07.611 Capture 3876 8 1 71 608 0:00:00.859 0:00:00.250 8:32:29.231 Capture 4988 8 1 71 628 0:00:01.000 0:00:00.328 8:09:15.555 Capture 4220 8 1 71 604 0:00:01.031 0:00:00.375 7:44:15.052 Why don't they close for hours?
	Andrew.
	IP Logged

Michel_K17 Moderator Group Forum Administrator Joined: 25 Jan 03 Posts: 1673	Posted: 30 May 07 at 1:02PM
	Hi, I will take a look. Capture.exe is started by the printer when it receives a new print job. Capture.exe waits to receive the printer data, and then converts it into a PDF. If yu send a lot of print jobs very quickly, then the Windows Print spooler may become overloaded, and may not send the printer dat right away, which is why you may have these Capture.exe's just there, waiting for the data to come through. There is a timer inside Capture.exe which will cause it to quit after a while if it does not receive any data, so they should go away by themselves, except that the PDF may not have been created. Anyway, I will take a look at it today, and I will see if there is anything I can do to help resolve the problem. Did you create the 380 batch printers by hand? That must have taken a long time! Finally, here is one more thing to consider: if the PDF files are created automatically (via code), I would make sure that you control how quickly and how many print jobs you place in the queue to make sure you do not overload Windows and your PC.
	Michel Korwin-Szymanowski EXP Systems LLC
	IP Logged

lovetski Newbie Joined: 18 Apr 06 Location: Russian Federation Posts: 30	Posted: 31 May 07 at 6:00AM
	Hi. As you see from my list, some of the capture.exe processes are waiting for 50 hours. This does not seem to be a timeout ;) We created printers manually gradually during a whole year. The files are created by a special printing program of a LIS (laboratory information system). We do not have any source code, neither any ways of controlling how it creates print jobs.
	Andrew.
	IP Logged

Michel_K17 Moderator Group Forum Administrator Joined: 25 Jan 03 Posts: 1673	Posted: 01 Jun 07 at 12:54AM
	Hi, Oops: yes you are right. Thanks for the additional info. I will run some tests here, and see what I can do to fix the problem. Cheers!
	Michel Korwin-Szymanowski EXP Systems LLC
	IP Logged

Using PDF reDirect
EXP Systems Forum : PDF reDirect : Using PDF reDirect