Dreamweaver CC 2017 Slow

[krestenb69596302]

Hi,

Am i the only one that experiences that the new Dreamweaver is extremely slow. When i open a standard bootstrap 3 design, i takes 7 seconds to open. And when the document is opened, it lags when i scroll in the source code - I only view source code - no preview/WYSIWYG. It feels lagging as if you start windows in safe mode without driver for graphic adapter.

I installed Dreamweaver CC2015.3 It opens the same document in 1 second. No lag and as fast as you would expect an text editor to be 🙂

Is it just my setup? or is anyone else have the same issues?

Im using a 8 core Xeon with GTX1060 graphic adapter.

[Preran · Accepted solution]

I checked with the product team, and they know that DW experiences slowness when handling a large number of files, or files from a remote location. They are investigating the causes.

Meanwhile, if there are other scenarios wherein you experience slowness, list them in this email thread, and I will log bugs for them.

Thank you for your persistence and patience while we resolve this issue.

Thanks,

Preran

[Homestar9]

Thanks for the update, Preran.  Knowing that the dev team is aware of the issue definitely makes me feel hopeful that someday there may be a fix.  Thank you also for participating in the discussion forums.

[jucra]

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=eyJ4NXUiOiJpbXNfbmExLWtleS0xLmNlciIsImFsZyI6Il...

[jucra]

I "think" I might have resolved the lag issue on my mac.

On my mac I am running a nice firewall  called "Little Snitch" and noticed that CC 2015 was added but CC 2017 was not in any of the rules.

So I added CC 2017 to the list of rules, went back to CC 2017 and no more lag during typing or clicking/selecting.

[Netoper]

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.

[Joyful_precision5D50]

Thanks. I ran the compatibility test on node.exe and windows 10 suggest to run it on compatibility mode for windows 8 apps. Code hinting was improved a little bit. But the overall speed continues a shame.

[dogdogrun]

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.

[KenThomas]

Same here... Dreamweaver is in an almost constant state of not responding... tempted to use Notebook to do my editing.  Ridiculous.

[zehrer00]

- 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)

[Arel]

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.

[Preran]

Hi Arel,

Just to be sure, are you on the latest update that was released this week? Also, are you trying to access files from a remote drive>

Thanks,

Preran

[Arel]

CC says I am up to date. The file is on my local machine. Thanks!

[jonburr]

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??

[jonburr]

(this is 2017.1 releases, build 9583)

[jonburr]

(the "actions" button in the Forum post meta isn't working in Safari/Mac/Sierre)

[ibytedk]

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!

[paul campagna]

This slowness and un-usabilty just started. What had Adobe done to cause this all of a sudden? More tracking, more "features" that just turn it into a snail?

It weas usable last Friday, but now EVERYTHING lags. I click, then wait...... click again and wait.... then the menu pops up fast two times and I go through the same thing!! Click, wait................

I've spent the last hour just rying to get it to work at all, without lagging. Shut off pretty much evefything but dreamweaver and no change. This is on a iMac  4GHz i7 with 32GB of ram. So it's not the average computer. So why is it slow? painfully sloooooowwwwww.

[Nancy OShea]

When DW starts acting weird, the first thing to try is Deleting Corrupted Cache in DW

http://forums.adobe.com/thread/494811

If that doesn't help, try Restore Preferences

https://helpx.adobe.com/dreamweaver/kb/restore-preferences-dreamweaver-cs6-cc.html

[ibytedk]

When CC 2017 starts acting weird. First thing to do is uninstall and install CC 2015. This removes ALL problems with lag, slow startup, slow saving, problems with handling many open documents.

On top of removing all you waiting problems, it adds back in code hinting and collering for ASP classic, XSLT

In fact the only thing I'm struggeling with is different CSS shorthand languages like SASS and LESS, bur then again. 2017 couldn't handle those right either.

Adobe, stop making things less effective and calling them new!

[jan theob47579031]

I used Dreamweaver CC 2017 with Win 10 64 bit. Most of the time Dreamweaver would not start and if it did it was horribly slow. I tried all solutions that have been suggested here and elsewhere. To no avail. I downgraded to 2015 and everything is okay now: up and running in seconds without serious problems.

[thomasjordanhill]

I am using Dreamweaver CC 2017 on a 16GB RAM MacBook 2014 i7 with 2GB Nvida graphics and struggling to preview a 9 file website without the scroll or css animations lagging in safari preview. Possible cause?

[Nancy OShea]

Did you try using another browser?

What is the URL to the online site?

[pziecina]

thomasjjjj  wrote

I am using Dreamweaver CC 2017 on a 16GB RAM MacBook 2014 i7 with 2GB Nvida graphics and struggling to preview a 9 file website without the scroll or css animations lagging in safari preview. Possible cause?

Css animations and any javascript animations are well know to cause problems, if badly written, over complexed, use old js or are simply too large in Safari browsers, and the main indicator of this, is problems with page scroll.

The first thing to try is commenting out the css and javascript for the animation. If this fixes the scroll problem, (after clearing browser cache) then please start a seperate discussion, and provide a direct link, (with css and javascript re-enabled) to the file on your hosting providers server.

It should be a link, as simply posting the code would not be ideal for diagnosis of such problems.

[aiseruchan]

Yeah it's slow for me, too. CS5 works faster for me than DWCC. The Live-Preview pisses me off so much, too.

[Dogvan]

I have the program both at home and at the office.  It's painfully slow at the office but it's just fine at home.  I'm doing code only so I'm using DW for a glorified text editor, basically.  At the office I had to install Atom because it does the same thing and DW is literally locking up my system, i.e. Windows every time I save a file or open a file.  For instance, I'm a habitual Alt-Tab window switcher and when I hit CTRL-S to save a tiny file in DW and then hit Alt-Tab over to Filezilla, the preview windows for fast-switching literally hang on my screen for 7-10 seconds until DW completes.  Obviously Windows shouldn't let Adobe crush the system like that, but I feel this is a clue to the root cause.

Some things that are different with my office installation may be relevant.  I'm on a domain login and I have network resources on the machine even though I have specifically excluded them for DW.  Only one site is defined and that is a local one.  I have nothing except code in my files.  I can tell DW is parsing image references and whatnot because it will pull thumbnails for hardcoded images in my code.  But I don't see how that could impact file save/open operations.  I suspect there's a problem in playing nice with a background resource scheduler in Windows.

Deleting the cache and even the full user settings folder did not help.