Spoolsv.exe and memory usage

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Running XP Pro SP2. As I print various reports, the size of the spoolsv as
seen under TaskMgr grows larger and larger. I know this should occur as I
sent a report to the spooler. But once the report is done, the memory is not
released. Since run everal reports a day, spoolsv eventually uses so much
memory, the system slows down and I get various membery warnings from
Windows. This has been occuring for a long time and on more than one
computer. If I reboot or stop/restart the service, then all is OK for awhile.

Note that this is different than cpu high usage that others have posted.

Any assistance will be greatly appreciated.
 
this is normally caused when the rendering module for the driver unloads
without releasing the memory used.

What printer model do you have? Is there a compatible driver you can
substitute?

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Hello!

Howard - JC Publishing said:
Running XP Pro SP2. As I print various reports, the size of the spoolsv as
seen under TaskMgr grows larger and larger. I know this should occur as I
sent a report to the spooler. But once the report is done, the memory is not
released. Since run everal reports a day, spoolsv eventually uses so much
memory, the system slows down and I get various membery warnings from
Windows. This has been occuring for a long time and on more than one
computer. If I reboot or stop/restart the service, then all is OK for awhile.
Click to expand...

Which application do you use for printing reports? Is it possible
to "print" reports to PDF files and then print them with Adobe Reader?

Roman
 
I have had the same problem but I think that it may have been solved by
turning off the option to spool print. After making the change I started the
report generation process and using the Task Manager watched the spoolsv.exe
stay at the same level instead of rapidly growing. The system appears to be
producing the reports as it should without any problems. Since the entire
report generation process can take over 20 hours to finish I left the job
running overnight just to see what happens. Try it if you can and let us
know if it works for you.
 
By having the reports run directly to the printer, the applications are not
usable until the report is completed. That would increase the amount of time
to do our work.
 
Back
Top