High CPU usage in the client software

KB Home   |   High CPU usage in the client software

Main.ClientHighCPU History

Hide minor edits - Show changes to output

Changed line 13 from:
# Go to the client directory in Windows. This will be be [@C:\Program Files\PaperCut NG\client\win=] or [=C:\Program Files (x86)\PaperCut NG\client\win@]
to:
# Go to the client directory in Windows. This will be be @@C:\Program Files\PaperCut NG\client\win@@ or @@C:\Program Files (x86)\PaperCut NG\client\win@@
Changed lines 11-12 from:
Follow these steps will disable some advanced graphics effects in the client that seem to cause the high CPU issue on some systems.
to:
Following these steps will disable some advanced graphics effects in the client that seem to cause the high CPU issue on some systems.
October 12, 2010, at 10:41 PM by 202.129.124.120 -
Changed line 16 from:
# Remove the "#" from the start of the line "#disable-gui-effects=Y".
to:
# Remove the "#" from the start of the line "#disable-gui-effects=Y". If you don't find this line, please add the line "disable-gui-effects=Y" at the end of the file.
Changed lines 3-4 from:
Some sites have reported issues in recent versions of PaperCut where the client software consumes 100% CPU. This issue, although not yet fully diagnosed, seems to related to graphics driver issues and the use of transparency on Windows. This issue seems to occur when ''fast user switching'' is enabled and an active login session is switched out. Consider one of the following solutions:
to:
Some sites have reported issues in recent versions of PaperCut where the client software consumes 100% CPU. This issue, although not yet fully diagnosed, seems to related to graphics driver issues and the use of transparency. This issue occurs when ''fast user switching'' is enabled and an active login session is switched out. Consider one of the following solutions:

!!! Stop using fast user switching

Reconsider the use of ''fast user switching''.  In a multi-user network environment (rather than home use), fast user switching can actually be a disadvantage as the inactive sessions consume resources. A full logout is usually what the user intended.

Deleted line 10:
Changed lines 22-25 from:
!!! Stop using fast user switching

Reconsider the use of ''fast user switching''.  In a multi-user network environment (rather than home use), fast user switching can actually be a disadvantage as the inactive sessions consume resources. A full login is usually what the user intended.

to:

Changed lines 1-2 from:
(:title If PaperCut Windows User Client Tool has high CPU usage :)
to:
(:title High CPU usage in the client software :)
Changed line 10 from:
# Go to the client directory in Windows. This will be be [=C:\Program Files\PaperCut NG\client\win=] or [=C:\Program Files (x86)\PaperCut NG\client\win=]
to:
# Go to the client directory in Windows. This will be be [@C:\Program Files\PaperCut NG\client\win=] or [=C:\Program Files (x86)\PaperCut NG\client\win@]
Changed lines 10-16 from:
* Go to the client directory in Windows. This will be be [=C:\Program Files\PaperCut NG\client\win=] or [=C:\Program Files (x86)\PaperCut NG\client\win=]
* Make a backup copy of the [@config.properties@] file.
* Open [@config.properties@] in a text editor.
* Remove the "#" from the start of the line "#disable-gui-effects=Y".
* Save [@config.properties@]
* Restart pc-client (the client executable).
to:
# Go to the client directory in Windows. This will be be [=C:\Program Files\PaperCut NG\client\win=] or [=C:\Program Files (x86)\PaperCut NG\client\win=]
# Make a backup copy of the [@config.properties@] file.
# Open [@config.properties@] in a text editor.
# Remove the "#" from the start of the line "#disable-gui-effects=Y".
# Save [@config.properties@]
# Restart pc-client (the client executable).
Changed lines 26-30 from:
[-keywords: client, CPU, 100% CPU, CPU hog, CPU hogging, advance graphics, gui effects, fast user switching   -]



to:
[-keywords: client, CPU, 100% CPU, CPU hog, CPU hogging, excessive CPU, fast user switching  -]



Changed lines 3-6 from:
The PaperCut Windows User Client Tool is thoroughly tested on a wide range of Windows versions, computers and graphics hardware. The User Client Tool's default settings work have been shown to work correctly on all of these configuration except for the cases described in this article.

The only problem that has been reported on the latest version of PaperCut is 100% CPU usage at various times such as logging in to the server. (If more issues are found in the future they will be reported in [[KnownIssues | Known Issues]]). If you see the PaperCut Windows client using 100% CPU then please try the following remedies.

to:
Some sites have reported issues in recent versions of PaperCut where the client software consumes 100% CPU. This issue, although not yet fully diagnosed, seems to related to graphics driver issues and the use of transparency on Windows. This issue seems to occur when ''fast user switching'' is enabled and an active login session is switched out. Consider one of the following solutions:
Added lines 7-9:

Follow these steps will disable some advanced graphics effects in the client that seem to cause the high CPU issue on some systems.

Changed lines 11-12 from:
* Make a backup copy of the config.properties file.
* Open config.properties in a text editor.
to:
* Make a backup copy of the [@config.properties@] file.
* Open [@config.properties@] in a text editor.
Changed line 14 from:
* Save config.properties
to:
* Save [@config.properties@]
Changed lines 17-20 from:
These steps will disable some advanced graphics effects in the client that a small number of graphics drivers cannot perform efficiently under some circumstances. 

If this does not work then replace config.properties with the saved backup version.

to:
''Note:'' If the client is locally installed, you may need to edit the local copy of the [@config.properties@] file.
Changed lines 21-22 from:
If you are using Windows fast user switching and more than one Windows user account is running the PaperCut client on the same computer at the same time then try rebooting the computer with only one account running the PaperCut client.
to:
Reconsider the use of ''fast user switching''.  In a multi-user network environment (rather than home use), fast user switching can actually be a disadvantage as the inactive sessions consume resources. A full login is usually what the user intended.
September 15, 2010, at 01:53 AM by peter - Changed sense of title
Changed lines 1-2 from:
(:title PaperCut Windows User Client Tool has high CPU usage :)
to:
(:title If PaperCut Windows User Client Tool has high CPU usage :)
September 15, 2010, at 01:22 AM by peter - formating
Changed lines 5-6 from:
The only problem that has been reported on the latest version of PaperCut is 100% CPU usage at various times such as logging in to the server. (If more issues are found in the future they will be reported in [[KnownIssues]]). If you see the PaperCut Windows client using 100% CPU then please try the following remedies.
to:
The only problem that has been reported on the latest version of PaperCut is 100% CPU usage at various times such as logging in to the server. (If more issues are found in the future they will be reported in [[KnownIssues | Known Issues]]). If you see the PaperCut Windows client using 100% CPU then please try the following remedies.
September 15, 2010, at 01:21 AM by peter - Made consistent with other kb articels
Changed lines 1-8 from:
(:title PaperCut Windows client has high CPU usage :)

The PaperCut Windows client is thoroughly tested on a wide range of Windows versions, computers and graphics hardware. The client's default settings work correctly on all of these configuration except for a small number.

On those Windows configurations where
the default PaperCut client settings has been shown to have problems, the symptom that has been observed is 100% CPU usage at various times such as logging in to the server.

If you see the PaperCut Windows client using 100% CPU then please try the following remedies.
to:
(:title PaperCut Windows User Client Tool has high CPU usage :)

The PaperCut Windows User Client Tool is thoroughly tested on a wide range of Windows versions, computers and graphics hardware. The User Client Tool's default settings work have been shown to work correctly on all of these configuration except for the cases described in this article.

The only problem that has been reported on the latest version of PaperCut
is 100% CPU usage at various times such as logging in to the server. (If more issues are found in the future they will be reported in [[KnownIssues]]). If you see the PaperCut Windows client using 100% CPU then please try the following remedies.
Changed lines 9-10 from:
* Go to the client directory in Windows. This will be be C:\Program Files\PaperCut NG\client\win or C:\Program Files (x86)\PaperCut NG\client\win
* Make a copy of the config.properties file in this directory.
to:
* Go to the client directory in Windows. This will be be [=C:\Program Files\PaperCut NG\client\win=] or [=C:\Program Files (x86)\PaperCut NG\client\win=]
* Make a backup copy of the config.properties file.
Changed lines 18-19 from:
If this does not work then replace config.properties with the saved version.
to:
If this does not work then replace config.properties with the saved backup version.
September 15, 2010, at 12:39 AM by peter - KB article for support ticket 17041
Added lines 1-33:
(:title PaperCut Windows client has high CPU usage :)

The PaperCut Windows client is thoroughly tested on a wide range of Windows versions, computers and graphics hardware. The client's default settings work correctly on all of these configuration except for a small number.

On those Windows configurations where the default PaperCut client settings has been shown to have problems, the symptom that has been observed is 100% CPU usage at various times such as logging in to the server.

If you see the PaperCut Windows client using 100% CPU then please try the following remedies.

!!! Disable advanced graphics features

* Go to the client directory in Windows. This will be be C:\Program Files\PaperCut NG\client\win or C:\Program Files (x86)\PaperCut NG\client\win
* Make a copy of the config.properties file in this directory.
* Open config.properties in a text editor.
* Remove the "#" from the start of the line "#disable-gui-effects=Y".
* Save config.properties
* Restart pc-client (the client executable).

These steps will disable some advanced graphics effects in the client that a small number of graphics drivers cannot perform efficiently under some circumstances.

If this does not work then replace config.properties with the saved version.

!!! Stop using fast user switching

If you are using Windows fast user switching and more than one Windows user account is running the PaperCut client on the same computer at the same time then try rebooting the computer with only one account running the PaperCut client.

----
''Categories:'' [[Category.UserClientTool|+]], [[Category.Troubleshooting | +]]
----
[-keywords: client, CPU, 100% CPU, CPU hog, CPU hogging, advance graphics, gui effects, fast user switching  -]



Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on March 27, 2013, at 06:05 AM
Printable View   |   Article History   |   Edit Article