Skip to main content
A
artoix
Known Participant
February 1, 2017
Question

Dreamweaver CC 2017 slow launch

  • February 1, 2017
  • 1 reply
  • 1906 views

I use Dreamweaver CC 2017 on MacBook Pro (16 GB, 2,3 GHz Intel Core i7, 15-inch retina, Late 2013). And the app launches incredibly slowly! It so long, that it feels as if Dreamweaver launch is something like 3D rendering. Do you ray-trace the code in multiple passes, or what? Look at the screen-recording I attach below — it took 1 min 20 sec for app to launch and show me just four html and scss files I have opened.

Dreamweaver CC 2017 launch time - YouTube

Please do something with that.

This topic has been closed for replies.

1 reply

Nancy OShea
Community Expert
Nancy OSheaCommunity Expert
Community Expert
February 1, 2017

In my experience, the first time you launch it takes a while to cache sites and sync settings, etc...  Thereafter, it should launch faster.  If it doesn't, turn off auto sync in Preferences and disable Enable Cache in your site definition settings. 

Also, keeping local files on the primary hard drive instead of an external gives better performance.

Nancy

Nancy O'Shea— Product User & Community Expert
A
artoixAuthor
Known Participant
February 2, 2017

Thank you, Nancy!

It wasn't the first launch, I updated to CC 2017 immediately when it was introduced. Slow launch just happens from time to time, and I would not say that at times when it launches too long I have a lot of other apps opened and my Mac is overloaded.

I'll keep monitoring it, and I'll try disabling Cache. Thanks!

A
artoixAuthor
Known Participant
February 3, 2017

A 2.3 GHz chip can only do so much at one time.   Closing other apps and background processes will definitely improve your Laptop's performance.  

Nancy


Even with all its functionality Dreamweaver is just a coding engine first and foremost. It even hardly can be called an IDE. And I don't think it's a good response to say "your MacBook Pro is too slow to run anything else except our coding engine". After Effects and Cinema 4D don't say that to me, they just work fine while doing really heavy work. So it's a really bad response. Guess what I choose: change coding engine or upgrade my (still quite good) MacBook Pro to something even more performant so a coding engine could finally allow me to code.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices