Skip to main content
sarobar_kasaju
Inspiring
November 7, 2016
質問

Photoshop CC 2017 Unusable slow

  • November 7, 2016
  • 返信数 66.
  • 150496 ビュー

I upgraded my Photoshop to CC 2017 today and since the upgrade it has been very very slow. When I click on File menu the dropdown menu appears like after 3-4 seconds. When I delete layer it take about 10 second. Zoom in and out are terribly slow. I work on Photoshop everyday hope to get the problem resolve as soon as possible.

Is there a way to downgrade to earlier version?

My computer details:

Windows 10 Pro

Processor: Intel i7-5960X

RAM: 32 GB

Graphic: NVIDIA GeForce GTX 780 Ti

SSD

このトピックへの返信は締め切られました。

返信数 66

Arturo Leone
Participant
November 22, 2016

I've found that (for me) Photoshop problems arise especially when Illustrator is open as if they were competing for resources. CPU is maxed out and the interface becomes extremely slow (or it freezes completely)

I'm on a Windows 10 machine with 16Gb ram, a couple of ssd (system and data, 200 Gb of free space each) and a Geforce GTX 1060 3Gb

Participating Frequently
November 21, 2016

I can't fit a screenshot of task manager here, too many CEPHtmlEngine and AdobeCEF to fit on the screen.

"there might be a commonality between the systems that are having problems."

Yep they have Adobe 2017 installed.

2015 working for most people, 2017 not working for lots of people, same computers, only the software changed.  Please report your hardware profile so we can see what you did wrong with your computer?

sonofmrsnak
Inspiring
November 21, 2016

I've given up on 2017 because of the slowdown. Tried all the Mac solutions. Never should have been released.

sonofmrsnak
Inspiring
November 21, 2016

2015.5 reinstalled and the program works fine now.

Adam Jerugim
Community Manager
Community Manager
November 21, 2016

Two more things to try (one-at-a-time please):

1.  Disable GPU - go to Preferences > Performance and uncheck "Use Graphics Processor" then quit and re-launch PS

2.  Disable Extensions - go to Preferences > Plug-Ins and ensure all the check boxes on that panel are unchecked (turn off Generator, Remote Connections, Allow Extensions to Connect to the Internet, and Load Extension Panels) - then quit and re-launch PS

Do either of these changes help with overall Photoshop performance?


Thanks,

Adam

Pete.Green
Community Manager
Community Manager
November 21, 2016

In addition to Adam's steps, I just wanted to up-level what Naveed reported working for him.

Go to Preferences (Ctrl+K) > Tools: Uncheck "Animated Zoom", "Enable Gestures", "Overscroll" and "Show Tool Tips" .

Does this help anybody else's CC 2017 performance?

Regards

PG

JacekPuzio
Participating Frequently
November 21, 2016

Nope.

JacekPuzio
Participating Frequently
November 21, 2016

Cropping is also slow as hell...

phhortress
Participating Frequently
November 22, 2016

My 2 cents.  I purchased Photoshop CC 2017 a week ago.  This is the first version of PS I have ever installed.  I am trying to edit a video and it is torture. This screenshot was taken while PS was running the video:

These are my system specs:

Not state of the art (not multi-core) but otherwise meets the published specs.  I haven't rebooted this much in years.  My scratch disc and file source disk are different.  I have 13 GB available on my primary drive (SSD) and 666 GB free on my storage drive (HDD).

Please help.

sonofmrsnak
Inspiring
November 22, 2016

I would try and get the last version. Not sure how that looks on a Windows machine from the Adobe app menu. Clearly, this version was not well-tested before release. Both PC and Mac users have been having significant issues.

Participant
November 21, 2016

Mid 2010 12 Core Mac Pro Tower with 64GB of RAM, several RAIDs, NVIDIA GeForce GTX 760 4095 MB, running Mac OS X  10.11.6

Everything was running fine until today's upgrade to 2017 versions of programs.

Premiere takes over 10 minutes to open,and then doesn't even function properly.    Meanwhile,  the 2015.5 versions of Photoshop and AE still open quickly. 

Here's a very small sample of the 100's  of Messages in that are compiling in Console:

11/20/16 10:15:23.625 PM Adobe Premiere Pro CC 2017[9528]: objc[9528]: Class IZAccessibleStaticText_Uniq is implemented in both /Applications/Adobe Premiere Pro CC 2017/Adobe Premiere Pro CC 2017.app/Contents/Plug-Ins/Common/VST3/AnalogDelay.vst3/Contents/Resources/AnalogDelayCore.bundle/Contents/MacOS/AnalogDelayCore and /Applications/Adobe Premiere Pro CC 2017/Adobe Premiere Pro CC 2017.app/Contents/Plug-Ins/Common/VST3/Phaser.vst3/Contents/Resources/PhaserCore.bundle/Contents/MacOS/PhaserCore. One of the two will be used. Which one is undefined.

11/20/16 10:15:23.629 PM Adobe Premiere Pro CC 2017[9528]: objc[9528]: Class IZApplicationDelegate_Uniq is implemented in both /Applications/Adobe Premiere Pro CC 2017/Adobe Premiere Pro CC 2017.app/Contents/Plug-Ins/Common/VST3/AnalogDelay.vst3/Contents/Resources/AnalogDelayCore.bundle/Contents/MacOS/AnalogDelayCore and /Applications/Adobe Premiere Pro CC 2017/Adobe Premiere Pro CC 2017.app/Contents/Plug-Ins/Common/VST3/Phaser.vst3/Contents/Resources/PhaserCore.bundle/Contents/MacOS/PhaserCore. One of the two will be used. Which one is undefined.

11/20/16 10:15:23.963 PM Adobe Premiere Pro CC 2017[9528]: objc[9528]: Class IZAccessibleComboBoxPopupItem_Uniq is implemented in both /Applications/Adobe Premiere Pro CC 2017/Adobe Premiere Pro CC 2017.app/Contents/Plug-Ins/Common/VST3/AnalogDelay.vst3/Contents/Resources/AnalogDelayCore.bundle/Contents/MacOS/AnalogDelayCore and /Applications/Adobe Premiere Pro CC 2017/Adobe Premiere Pro CC 2017.app/Contents/Plug-Ins/Common/VST3/SimpleMastering.vst3/Contents/Resources/SimpleMasteringCore.bundle/Contents/MacOS/SimpleMasteringCore. One of the two will be used. Which one is undefined.   

11/20/16 10:15:24.643 PM Adobe Premiere Pro CC 2017[9528]: objc[9528]: Class IZAccessibleWindowStack_Uniq is implemented in both /Applications/Adobe Premiere Pro CC 2017/Adobe Premiere Pro CC 2017.app/Contents/Plug-Ins/Common/VST3/AnalogDelay.vst3/Contents/Resources/AnalogDelayCore.bundle/Contents/MacOS/AnalogDelayCore and /Applications/Adobe Premiere Pro CC 2017/Adobe Premiere Pro CC 2017.app/Contents/Plug-Ins/Common/VST3/VocalEnhancer.vst3/Contents/Resources/VocalEnhancerCore.bundle/Contents/MacOS/VocalEnhancerCore. One of the two will be used. Which one is undefined.

11/20/16 10:17:50.788 PM Adobe Premiere Pro CC 2017[9528]: objc[9528]: Class DigiRegTextField is implemented in both /Library/Application Support/Adobe/Common/Plug-ins/7.0/MediaCore/Digieffects/DE_AgedFilm.plugin/Contents/MacOS/DE_AgedFilm and /Library/Application Support/Adobe/Common/Plug-ins/7.0/MediaCore/Digieffects/DE_ElectricalArcs_CS5.plugin/Contents/MacOS/DE_ElectricalArcs_CS5. One of the two will be used. Which one is undefined.

11/20/16 10:18:03.212 PM Adobe Premiere Pro CC 2017[9528]: objc[9528]: Class DigiRegTextField is implemented in both /Library/Application Support/Adobe/Common/Plug-ins/7.0/MediaCore/Digieffects/DE_AgedFilm.plugin/Contents/MacOS/DE_AgedFilm and /Library/Application Support/Adobe/Common/Plug-ins/7.0/MediaCore/Digieffects/DE_NightBloom_CS5.plugin/Contents/MacOS/DE_NightBloom_CS5. One of the two will be used. Which one is undefined.

11/20/16 10:18:06.835 PM Adobe Premiere Pro CC 2017[9528]: objc[9528]: Class AboutWindowControllerNew is implemented in both /Library/Application Support/Adobe/Common/Plug-ins/7.0/MediaCore/Digieffects/DE_AgedFilm.plugin/Contents/MacOS/DE_AgedFilm and /Library/Application Support/Adobe/Common/Plug-ins/7.0/MediaCore/Digieffects/DE_SchematicGrids_CS5.plugin/Contents/MacOS/DE_SchematicGrids_CS5. One of the two will be used. Which one is undefined.

11/20/16 10:18:17.263 PM Adobe Premiere Pro CC 2017[9528]: Unable to find filter reference documentation "".

11/20/16 10:20:47.130 PM Adobe Premiere Pro CC 2017[9528]: objc[9528]: Class PrivilegedExec is implemented in both /Library/Application Support/Adobe/Common/Plug-ins/7.0/MediaCore/Trapcode/3DStroke.plugin/Contents/MacOS/3DStroke and /Library/Application Support/Adobe/Common/Plug-ins/7.0/MediaCore/Trapcode/Form.plugin/Contents/MacOS/Form. One of the two will be used. Which one is undefined. 

11/20/16 10:23:52.528 PM AdobeCRDaemon[9529]: File Directory used for checking the value /Users/playback/Library/Logs/Adobe

Terri Stevens
Legend
November 21, 2016

there was a major update to Premiere and After Effects last week are you running those or the original build?

Known Participant
November 21, 2016

Add me to the list of customers completely pissed about this pitiful "update."  Do you nitwits do any testing at all before releasing these disasters?  Everything slow.  Brushes slow, any blurs slow, anything I do slow slow slow.  And no I don't have other programs running in the background.  Utilization sits at 1-2% while not doing anything in photoshop, then as soon as I do, jumps up to about 40% and stays there for the 30 seconds or so it takes to do whatever the task it. 

Adobe is just embarrassing itself at this point.

Terri Stevens
Legend
November 21, 2016

I can understand your frustration, but how do you expect anyone to help if you don't as much as say the platform and OS your are on? ~Maybe you just want to be heard. If your problem is that severe then you might benefit from talking to an Adobe Tech. Use the 'chat' option in the link below and the technician may be able to remote desktop to your machine and examine it in a way not possible using the text based dialogs we have on this forum.

https://helpx.adobe.com/contact.html?step=PHSP-PHXS_downloading-installing-setting-up_licensing-activation_stillNeedHelp

Terri Stevens
Legend
November 19, 2016

Guys, with respect, if you want to get this problem fixed it is no use just saying it runs slow and is unusable. If your system is running slow there will be evidence why and it will show up in 'Task Manager' on Windows systems and the 'Activity Monitor' on a Mac. What we need is an indication of what your CPU and hard disk are doing while Photoshop is running. Pete and Adam above have already stated this but so far nobody with the problem has submitted here evidence from their system. What you need to do is take a screen capture and upload it here. You don't need special software to do that, just run Activity Monitor or Task Manager and press PrtScn or print screen on your keyboard to copy to your clipboard, then in a thread here press command-v or ctrl-v to paste the capture into place.

This is the kind of thing the engineers need to see. The following is from Windows

Harmonysmom
Participating Frequently
November 20, 2016

You can add my name to the list of frustrated people. Photoshop CC2017 is excruciatingly slow when doing just about anything. I too am getting the spinning wheel of death. I'm on a iMac (Retina 5K, 27-inch, Late 2015) running OS X El Capitan with a 3.2 GHz Intel Core i5 processor and an AMD Radeon R9 M380 2048 MB graphics card, which I recently upgraded to after Photoshop made my old Mac obsolete with upgrades that required a more efficient graphics card. Ugh. I'm not a techie ~ somewhere between your old grandma and a computer geek, but more towards the old grandma side. Anyway, help! I'm enclosing four screen shots of the activity monitor since I wasn't sure which tab would provide the information you seek. See what I mean about the grandma description?

I was trying to scroll through fonts when I took these screen shots. Other than that, it has been SLOW while trying to move a layer up and/or down, while trying to move the contents of a layer with the move tool and with free transform, and while just scrolling through layers in general.

Here goes:

Terri Stevens
Legend
November 21, 2016

Hello,

Thanks for posting all that data. I'm afraid I can't give you a magical solution but it looks to me that your problem is down to excessive writes being made to your hard drive(s) I'm mostly a Windows users and not therefore very familiar with Mac processes but both the kernel_task at 4.57GB and Launched process at 7.10GB look very high to me. Try disabling all the Adobe startup process' as described in my post from the 11th Nov above (it's illustrated for Windows but can also be done on a Mac) and restart the computer. If this makes a difference Photoshop will work fine but the library panel may be a little flaky . This might serve as a temporary measure until Adobe work out exactly what is going on with the slow startup problem.

Participant
November 19, 2016

I was having the same issue on a Mac laptop. It was my first time using Artboards and everything I did would get the spinning color wheel for 5 seconds. I opened a new file not using the Artboard feature and now it is working fine.

jbm007
Community Expert
Community Expert
November 21, 2016

General question:

Are people working in 8 bit mode or 16 bit mode.

RGB mode or CYMK mode?

I have noticed that PS memory usage explodes when working on 16 bit files.

Just curious.

RJLeslie
Participating Frequently
November 21, 2016

I am working 16bit RGB.

Having turned off Font preview, things are working slightly better, though not as 100% as expected. Yesterday it got so slow that it wouldn't save files - stuck on 0% for over 20 minutes. Just spinning ball. Tried to access activity monitor but the machine was so locked up, this wouldn't even display. Forced quit Photoshop and Kernel_Task was running flat out. Restarted and all was back to normal and has been working "OK"  so far today.

Richard.

MacOS Sierra, MacBook Pro Mid2014 16GB, GT 750M

November 19, 2016

Sorry Adobe, I know you don't want to hear this but the CC 2017 updates broke several applications.

In the morning I was running 2015, no issues.  Installed the CC 2017 updates and Photoshop became slow and unusable.  I've unchecked the GPU and done the font thing above and it is still unusable.

The system hasn't change, the tasks in task manager are the same as this morning.  Something is broken with the update.

Recommend to anyone NOT to install the CC 2017 updates, I haven't got time to run beta on badly tested software updates and so am re-installing all the 2015 apps until adobe figures it out.  Good link above for accessing previous versions, much appreciated, now, after a morning loss, back to work for me!

Participant
November 19, 2016

How can I get 2015 when I didn't check to save previous versions?