Skip to main content
Known Participant
November 10, 2016
Answered

InDesign CC 2017 slow

  • November 10, 2016
  • 63 replies
  • 80483 views

I am having issues with InDesign CC 2017 being extremely slow. If I click on a font the beachball just spins... I tried working in it for a few hours but it is killing me and went back to the previous version.

I use Suitcase Fusion and turned off Typekit. I am running Mac OS Sierra.

Is anyone else having this issue? I can't find any complaints online.

Thank you

    This topic has been closed for replies.
    Correct answer SEEKAY

    Hello all,

    This has worked for me - cheers

    El Capitan 10.11.6

    iMac (27-inch, Mid 2011)

    3.4 GHz Intel Core i7

    16 GB 1333 MHz DDR3

    SSD

    AMD Radeon HD 6970M 2048 MB

    63 replies

    rdolishny
    Participating Frequently
    March 31, 2017

    I ended up uninstalling 2017 and installing 2015.

    Seems to be working.

    It felt like a Wacom bamboo issue, but after reading this thread I think it's a far greater issue.

    Participant
    March 30, 2017

    I'm writing a text book with 340 pages in Norwegian. I have used Indesign for many years. Now suddenly Indesign is so slow I can't work any more. None of the tips mentioned above have helped. Very disappointing to experience this.

    Participating Frequently
    March 28, 2017

    Exact same problem here, contacted adobe about it and they said it's related to our network so they can't offer us support...

    Many mac running the lastest OSX and InDesign have the same problem here, as soon as they are connected to our server, it's beachball hell. If we unmount the server for the mac, problem's solved... but we need our server connected in order to work.

    Adobe Please do something about this, it's a huge issue for us and your software is not working as advertised, and we are paying too much money to adobe for them to ignore our complaints.

    White-RSC
    Participating Frequently
    March 29, 2017

    stfchampagne  wrote

    Exact same problem here, contacted adobe about it and they said it's related to our network so they can't offer us support...

    Many mac running the lastest OSX and InDesign have the same problem here, as soon as they are connected to our server, it's beachball hell. If we unmount the server for the mac, problem's solved... but we need our server connected in order to work.

    I'll pile on here and say that this is exactly my issue also. I'm in an office of around 10 graphic designers, and if any of us are connected to our server, it's beach ball for 90% of the time I'm in InDesign CC. If I disconnect from the server, the problem goes away immediately. It's like InDesign is constantly trying to do *something* in the background while InDesign is running. Me and my I.T. team have tried everything, but still can't find the issue.

    If we find something, I'll post here ASAP.

    detailed_Cascade16B8
    Known Participant
    March 29, 2017

    I've done a fun little screen capture, is this the sort of thing that the rest of you are seeing? Here's the link:

    https://dl.dropboxusercontent.com/u/574262/dump/Indesign_2017_1.mp4

    The UI locks up at about 20s, for over a minute, so it's not very interesting! The frenzied mouse movement is me trying to get the UI to wake up. I get a bit of interactivity back at 1:25, for about 15 seconds, then it locks up again. Needless to say I've downloaded the last working version (2015.1), this is working fine.

    Using Windows10, 64Gb RAM, dual titan-X (Pascal) graphics cards, 1Tb SSD, 4Tb HD, A3 wacom tablet.

    Participating Frequently
    March 28, 2017

    The same issue here...beach ball on every click.  I've no idea what to do...it was fine yesterday!

    We all know that WHEN IT WORKS Adobe software is amazing but when it doesn't...which is all too often considering the monthly outlay, we al know that their support is crap...or should I say TOTALLY AWFUL....or TOTAL CRAP!  Embarrassingly so!  How many staff have been commenting on this post!!!  Just one response I think!

    It's OUR fault though....we put up with it because in the main, we HAVE to put up with it, they have us over a barrel as there are no viable alternatives - Quark?...good luck, that's a bigger a piece of s**t and is soooo not an option.

    It is just such a shame Adobe don't give a s**t about us...and they do have us over a barrel...i KNOW that, You ALL know that.

    Suck it up peeps...or take a stand and switch Applications...i dare you!

    rickhino
    Inspiring
    March 28, 2017

    I have actually removed InDesign from my development process.  I am creating electronic books in PowerPoint.  Actually reduces my development timeline.  I still use Photoshop, Illustrator, and Animate, but am looking for alternatives.  We pay too much money to Adobe to be treated in this manner.

    Participating Frequently
    March 28, 2017

    Good work Rick..I Wish I could but when Suppliers and Client require it...I am a bit stuffed!

    I admire you very much...it would be great to find hooky copies of CC that work!!!  It goes against my principles but...I would use them!  A sad sign of the times...how being treaty so poorly can lead to such thoughts!

    Susan Loncar Design
    Known Participant
    March 18, 2017

    I tried reinstalling CC 2017. I tried downgrading to CC2015. No luck. Finally, today I re-installed my old student version of CS6. Amazing! I finally can work with no interruption or spinning rainbow beach balls of delay, delay, delay. CS6 is my happy place right now ...

    Participating Frequently
    March 14, 2017

    OK, I swore I wouldn't be on this thread again, but Mother Nature intervened. Let me explain...

    Today, in the Boston area, the latest Snowmaggedon storm limped by. With work-from-home looming, I decided to take one of these beachballing babies home with me. To my complete befuddlement, it has worked flawlessly. Indesign zoomed through the day with nary a wee pause. I'm no IT guy, but this seems to indicate a network-related issue.

    What I can't figure out is what could have changed on our work network when these problems started appearing. We hadn't been doing any work or made changes to the network or anything that I know about. Also, why is this problem not showing up on all our Indesign machines? Why is it so inconsistent and sporadic? What happened to Malaysian Air 370? All mysteries.

    So, I suppose Adobe is not entirely wrong blaming users' networks for the problem. But why would this have suddenly appeared with some recent version update? Why with Indesign? Why so unpredictable?

    Whatever the heck is going on, it's absurdly frustrating if you are dealing with this issue. The one thing I haven't tried yet, but might because it's probably worth it, is to completely wipe one of the machines and build everything up from scratch, documenting everything along the way. Might not make any difference, but it might save us a few brain cells.

    Then again, I still have my old mechanical paste-up tools - Rubylith, waxer, One Coat, Bestene, Xacto... maybe I'll just go back to basics...

    Thanks, Adobe!

    rickhino
    Inspiring
    March 15, 2017

    All well and good, but you're stating that Adobe not being entirely wrong blaming users' networks let's them off too easily.  If this were truly a user network issue, Adobe would have sent in one of their fan-boy minions to provide us with network settings leading to a fix.  That won't happen because they'd rather we didn't know what was going on through the back door.  Ask your IT department to place a sniffer on your computer while using UnDesign.  It's an interesting little exercise.

    Participating Frequently
    March 16, 2017

    Didn't intend to give Adobe a pass on this. Obviously something is wrong and it's hitting a wide swath of users and it's not due to user incompetence or problems with networks (that worked perfectly fine with previous versions of the software). Adobe identifying the user's network as the source of the problem is not inaccurate. It's not "right", but also not incorrect.

    What is so amazing about this is we can have two nearly identical computers running on the same network, working on the same files, but one lives in beachball hell, the other glides along completely normally. Removing the misbehaving machine to a completely different network setup fixes the problem.

    Again, I'm considering a completely fresh install of everything on this problem computer, just to see if it makes a difference. If I try this, I'll report back...

    Participant
    March 14, 2017

    This is absolutely terrible, working on a server (with a super fast fiber-optic connection) and I get this beach-ball hang at least once every 5-10 minutes, for around 5-10 seconds. That's fr199in' a lot during the whole time since this CC17 update came. I suspect it has something to do with the data-rate the program is using while constantly updating the previews, links/images and that kind of stuff.

    (Yes, working locally fixes the problem but there is a reason why we have these servers to work on, certainly beats that purpose...

    On top of that Creative Cloud is a proud modern-day internet-based service that doesn't seem to be able to work on the internet LOL)

    Participant
    March 14, 2017

    I have been having this problem for ages. I finally found a way to fix it (at least for now). I have removed all variants of Minion Pro from my computer, except "Regular." I now need to substitute a different font in my documents. Ugh. I have used Minion Pro as my Go-To font for years. However, if that is what is needed to fix the problem, I guess I can live with it.

    RG user
    Participating Frequently
    March 9, 2017

    Just curious what computer you are using for the slow reaction.  The HP we are using it on works fine. It is the Dell on which we have a problem. Both are on the network. Wondering if this makes a difference.

    Participating Frequently
    March 8, 2017

    This is probably the last time I'll post here since it clearly is making no difference as far as Adobe is concerned...

    For those struggling with this issue, we have determined on the two machines impacted by this (of 5 we have running 2017), the ONLY consistent "fix" is to work locally. The size of the document, its contents, the fonts used, etc. seem to make no difference. It might function perfectly fine for a period of time, then suddenly (and seemingly with nothing causing the change) start the beachball dance.

    The inconsistent appearance of the issue and the fact that it has only impacted two systems so far just makes it all the more frustrating. Open a document on one machine and it works fine. Open it on one of the "bad" installs and it tests one's patience...

    NOTHING in our network was changed from before the problem appeared to correspond to the initiation of the issue. The installation of 2017 started the problem (or maybe it was 2015 - hard to recount the timeline at this point).

    Good luck to you all... To reiterate - "work locally" has been the only thing that has worked consistently us.