Skip to main content
Participant
December 28, 2018
Answered

High CPU usage after saving an image

  • December 28, 2018
  • 1 reply
  • 953 views

On a Gigabyte Aorus Master Z390 motherboard with i9 9900K, 64GB RAM, NVidia Quadro P2000, with CC 2019, Windows 10 Pro 1809,  I have this strange behaviour: after saving or exporting an image, the CPU usage in Task Manager raises to 9-12% and remains stable, even if I close all open images and Photoshop is totally idle.

The increment occurs after many seconds, sometimes after 20-30, sometimes after 60-90, but sooner or later it will suddenly jump to 9-12% and the only solution is to close Photoshop.

The same occurs with Illustrator and InDesign.

I've uninstalled and reinstalled the Creative Cloud app, nothing has changed. I've unistalled and reinstalled Photoshop, nothing (in both cases I've used the Creative Cloud Cleaner tool.

I've replaced the com.adobe.DesignLibraryPanel.html folder content with the DL224.zip files. No change.

I've updated the motherboard BIOS and the P2000 drivers. Windows is fully updated.

I've checked for malware or virus, nothing, but in any case the system works fine with all other applications and programs.

Any suggestions?

PS: I want to add some more information. I have a NVMe drive, SSD drives, USB drives and a network server. Saving to any of these makes no difference. Also, I have two monitors.

And also, when Photoshop is running, expanding its line in Task Manager shows "many" sub-programs, usually 16: 2 Adobe Photoshop CC 2019, 9 Adobe CEP HTML Engine, 1 Adobe Dynamic Link Manager, 3 Adobe Spaces Helper, 1 Console window (command prompt), 1 Node.js Server-side Javascript.

On my Surface Pro, the list is much more compact: 1 Adobe Photoshop CC 2019, 2 Adobe CEP, 2 Adobe Spaces Helper, 1 Adobe IPC Broker, 1 "Namefile"@100%.

This topic has been closed for replies.
Correct answer MAX216

I answer myself: I found out that the "intel optane pinning explorer extensions" were automatically installed during some update operation. Unfortunately, I do not have any Optane hardware and therefore the associated dll, iastorafsserviceapi.dll, was probably continuously trying to "pin" something  somewhere. And this also explains why the CPU usage increment was "delayed".

Uninstalling those extensions seems to have completely cured the problem.

1 reply

MAX216AuthorCorrect answer
Participant
December 28, 2018

I answer myself: I found out that the "intel optane pinning explorer extensions" were automatically installed during some update operation. Unfortunately, I do not have any Optane hardware and therefore the associated dll, iastorafsserviceapi.dll, was probably continuously trying to "pin" something  somewhere. And this also explains why the CPU usage increment was "delayed".

Uninstalling those extensions seems to have completely cured the problem.