Dreamweaver CC 2017 Slow

It's painfully slow. And it has just become slower and slower with every upgrade. Nice to see that you can roll back to CC 2015. I will do it this instant.
On top the support for many types of code, including classic ASP has gone.

So you made you product both slower and less usable.

Nice going!

Deleting objects in the editor takes a long time. Deleting objects using the DOM panel takes longer. Deleting more than 3 objects in the DOM panel crashes Dreamweaver

Deleting one selector in the live view panel can take fifteen seconds. This is unacceptable performance. What the heck is going on in the background that it can't just execute the command??

Same issue for me: Dreamweaver CC2017 takes at least a minute to open a 5KB file in a site that has 6 pages. Any time I open Dreamweaver there is at least 1-2 minutes of rainbow wheel time of waiting. So, then when I try to open a document, there is another 1-2 minutes of rainbow wheel time; work flow is HORRIBLE!

I am using a mid 2015 Macbook Pro, 2.8 core i7, 16GB memory, 1TB SSD and 2/3rds of that storage is available. There weren't any of these types of issues until the CC 2017 update, so definitely there is some problematic coding in the software.

- W10, i7, 32GB, SSDs, CC2017.0.1 German Version

Using 2017.0.1 since few days:

- Not a rocket but performance much better

- no delays program start and close

- opening and working with more than 20 html-files still slow

- Edit mode causes a flickering screen - but editing live mode is ok? Hmmm ...

One more bug:

If you are opening more than one html-file the template (e.g. <!-- InstanceBegin template="/Templates/template_ushikes.dwt" codeOutsideHTMLIsLocked="false" -->) of the second file isn't locked.That's a problem if you want zu change (batch) all files only outside the template or if you want to format the code only outside the template.

Next one:

Optimizing Word-HTML changes <table class=xxxxx> in <table> -> class is gone forever (div's ok)

So frustrated with Dreamweaver CC 2017 it's slow and hangs up constantly. Exhausted trying to find solutions to fix the issues I'm experiencing. Reverting back to Dreamweaver CC 2015.

same problem here. DW 2017 is slow like snail.

i use home nas server and when DW start, every my connection to local nas slows down.

my solution. I do not even know what it is "node" and what it is used in DW (evented i/o for v8 javascript... two processes in task manager). i just disabled this with rename folder method. simply rename folder "node" in C:\Program Files\Adobe\Adobe Dreamweaver CC 2017 to "node_disabled". and viola. DW is now like rocket!

have fun and much comfortable programing like me

EDIT: ok, I experimented a bit. probably is not well forbid the functionality of the node. i renamed folder back to "node" and then set for node.exe file "run as administrator" (right click on the node.exe > properties > compatibility > run this program as an administrator) now is DW still fast and node is not disabled.

i use dell inspiron 13 (7359), i7, 8gb ram, 256gb ssd, win10

EDIT2: sorry. last time, i promise I've found that the node is used for the javascript linting. maybe for something else too, but don't know. when i set node.exe to run as admin, the node is not start with DW and JS linting not working. later I found out what the problem is. In my case, the problem is the path to the project. as i wrote, my projects is stored on local server (nas). I have created a network drive with letter W. then in project i define path to project with W://web/site.com/ (for example). but this is wrong. i must path defined as \\nas\site.com\ (nas is name of my server, or i can use server IP \\192.168.1.100\site.com\, It does not matter). then everything is in perfect order and DW work fast with node.exe running and js linting too.

I am also encountering click/typing lag in my DW 2017 version. I have a post here also: https://forums.adobe.com/message/9277320#access_token=eyJ4NXUiOiJpbXNfbmExLWtleS0xLmNlciIsImFsZyI6IlJTMjU2In0.eyJmZyI6Il…

Hello All,

I spent some time and came up with an experiment that we can all run to re-create the DW 2017 sluggish behavior problem.  Ideally you'll want to run the experiment with both DW 2017 DW 2015 installed on your machine to compare performance. 

Hopefully someone at Adobe will also run this test (wink wink, nudge nudge)!

Here's how to run the experiment:

1. Load up Chrome and open a new incognito window.

2. Visit the web site https://adwords.google.com (this is the Google AdWords home page. It will be our testing page)

Side note: The reason I picked this page is because it's got a lot going on here and should be enough to stress the HTML parser and show a measurable difference in performance between DW versions.   You could run this test with any other complex HTML page if you want.

3. Save the web page to your desktop by clicking CTRL + S (or click the browser menu > more tools > save page as...).  Make sure to save the complete web site in the save dialog options.

4. Once you've saved the page to your desktop, right click on it and open it in Dreamweaver 2017.

5. Play around with the source code, experiment between code view, design view, split view, etc.  Warning: this makes my copy of DW run at a snail's pace and I have a pretty beefy machine.

6. Now close DW 2017 and open the same file in DW 2015. 

7. Again, play around with the source code, experiment between code view, design view, split view, etc.  Notice any difference?

What does this test prove?

Well well all know that the HTML parsing engine that is in DW 2017 is different than 2015 and it's obvious that the new engine can't handle complex web pages with many external files referenced as well as the old version of Dreamweaver did.  This test was designed to make Dreamweaver work hard intentionally and probably isn't a realistic work example.  You may note that If you decide to run this test without saving the "complete web site" and instead just save the HTML you will notice that DW performs much better. I believe the key to this is the number of included external file references (.js, .css, etc...) that DW has to parse and deal with.

Are there any workarounds?

Not really. However feel free to experiment with your DW 2017 configurations. Experiment with turning off code coloring, validation, etc... maybe there's a magic bullet that we can temporarily disable until Adobe comes up with a fix. One thing you could do is temporarily comment out or remove your external javascript and css files. Assuming that is the problem here it may make DW 2017 perform better.

Hope this helps! Feel free to post your test results and thoughts.

My Dw 2017 is also very slow on my Mac Mini (mid 2011,16GB RAM, 2.7GHz). My Mac's Activity Monitor shows a "node" process that has Dw as its "parent process" and it is fluctuating between using about 95% to over 100% of my CPU. I have only 4 small html files open in Dw17 at this time. Is the only solution to this to downgrade to 2015? I did not have this problem with 2015.

Same problem with the german version ... W10 - i7 - 32 RAM