I'm on a high end Mac Pro early 2008 full of RAM under Mac OS X 10.8.5. Don't know why Dreamweaver CC is so slow to open a file. Anytime get the multicolor circle and need 10 to 20 seconds to open any file. Dreamweaver is useless in my case and nothing fix this problem. Delete cache, restart, re-configuration of everything. Install updates. Nothing works. Dreamweaver CC is tortoise. Any idea?
Is this happening with all sites & all files or just a few?
Is this happening with a new, blank document?
Thank you for your kindly reply.
I found the problem with your help but don't know how to resolve.
Dreamweaver CC slows because have trouble to load css conected files with decent speed.
This is the test:
1) After deleting this tag <link rel="stylesheet" type="text/css" href="css/style.css" media="all"> then the webpage loads as expect and Dreamweaver CC recover the speed (no problem with js files).
2) When check style.css the code that have problems are this:
@import url('./scaffolding.css'); /* Import Bootstrap (Responsive Grid System) Stylesheet */
@import url('./base.css'); /* Import Basic Styles, Typography, Forms etc stylesheet */
@import url('./blox.css'); /* Imports blox Stylesheet */
@import url('./flexslider.css'); /* Imports flexslider Stylesheet */
@import url('./prettyPhoto.css'); /* Imports prettyphoto Stylesheet */
@import url('./slide1.css'); /* Import LayerSlider Stylesheet */
@import url('./icomoon.css'); /* Imports icomoon Stylesheet */
@import url('./main-menu.css'); /* Import Menu Stylesheet */
@import url('./elements.css'); /* Import Elements stylesheet */
@import url('./pages.css'); /* Import Pages stylesheet */
@import url('./icon-box.css'); /* Import Icon Boxes stylesheet */
@import url('./shop.css'); /* Import Shop stylesheet */
@import url('./blog.css'); /* Import Blog stylesheet */
@import url('./portfolio.css'); /* Import Portfolio Stylesheet */
@import url('../layerslider/css/layerslider.css'); /* Import LayerSlider Stylesheet */
If I delete all @import url then works properly and the issue is gone, but need @import don't want to delete it.
Keep in mind that I'm using Bootstrap 3 and there's a lot of @import url but seems to be Dreamweaver can't manage this with the correct performance or need to be reconfigure.
Creating a new file also works properly.
Check this article "@import has a negative impact on web page performance": http://www.stevesouders.com/blog/2009/04/09/dont-use-import/
But is not a reason for Dreamweaver to have a slow performance If someone want to use it.
If I do this: View > Style Rendering > untick Display Styles. Don't correct the problem.
I apply the updates and all the process shows was applied successfully but if I check with the get info some application still on xx.00 instead of xx.02 or current updates. For example, Illustrator is v.17.02 on About Illustrator but checking get info on Finder is 17.0.0. I think all updates are applied correctly but see this differences when check it. Adobe Application Manager said: "Updates: Your applications are all up-to-date as checked: less than a minute ago. This differences was the same on CS6 when updates offline the applications on Mac OS X.
@TOM Adobe -
Thank you for your help.
I updated successfully all CC soft and fix update process.
Yes I have now v.18.104.22.16866 on Dreamweaver CC.
But the performance is tortoise's speed. Takes a lot to open files.
And scrolling is slow too... It's takes 5 to 10 seconds to switch from one open file to another open file. Selecting text in code view takes near 5 seconds for take effect. Very annoying.
With this slow performance Dreamweaver CC is useless.
Download the test file from here:
As a temporary work around, disable CSS to see if this improves performance.
View > Style Rendering > Disable Styles. This will allow you to work with un-styled pages in Design View. But it won't effect either Live View or Preview in Browsers.
In code view take A LOT of time to change anything.
Seems to be Dreamweaver CC is for little sites only. Check the site I upload and you wiil see the paralytic freeze procedure each time you want to edit or load something.
When you load a big site lost performance and can't manage with decent speed. Adobe adds features and reduce performance.
For what it's worth Tom, I work with big sites, too. But I rarely use @import CSS. I have yet to see any real benefit to them. I much prefer direct links to external styles and have no performance problems with this workflow.
But that means the user must customize any site for working on Dreamweaver to get a decent speed. Need to change all @import CSS to direct links and waste time on this procedure to avoid slow performance.
I'll wait it is a solution for this.
Don't accept a poor performance of speed that must wait and wait to make any changes.
Thanks for your help.
Check this. After changing all @import to <link href= on each pages the slow performance continue.
If you press refresh button need to wait near ONE MINUTE to get control again of Dreamweaver. All is freeze.
Clicking from files panel to code view have a large delay too. Scrooling have delay.
Any click of mouse have large delay to take effect on code view. If you drag and drop an image from files panel to code view take near 30 seconds to place it.
One of my colleagues have the same speed problem of slow performance an want to downgrade to Dreamweaver CS6. He was very upset and said, must use BBEDIT to walkarround this problem as Application's sustitution of Dreamweaver CC. He said code editing is useless on Dreamweaver CC because this "paralysis"'s of performance. I said to my friend to wait Adobe Team to fix this bug, but still waiting. Don't see any update yet.
Depends of the site you load on Dreamweaver CC for Mac OS X can have more or less speed for editing.
The real point is... always got the multicolor wheel cursor that means "you must wait" and 30 to 40 seconds of delay or more to wait Dreamweaver to return control to the user.
Try to use the refresh button and will see near 40 seconds if you have a big site. Freeze all the the Mac.
This important and unpredictable bug converts Dreamweaver on NightmareWeaver.
Another problem is Dreamweaver CC don't "forget" the linked CSS files. For example, after linking a CSS file and delete it then it's shows on Dreamweaver and can't find a way to delete the relationship. Clear preferences, re-enter all the configuration from scratch, nothing works. I`m sure the file was deleted, but Dreamweaver don't get "notice" of that.
Any updates on this? I'm having this same problem on a macpro 1,1 running 10.7.5. I've tried all the above fixes and then some with absolutely no success. Dreamweaver runs so slowly it's unusable. Activity monitor reports it as not responding constantly and trying to do a folder-wide find/replace took at least 20 minutes!
Please let me know when you have a solution to this issue as well. I have had this issue with Dreamweaver ever since Mavericks and the Dreamweaver update.
I do NOT use @import code (don't use bootstrap)
With a recent update my pages seem to load faster... but all I have to do is click around on various images on my page within Dreamweaver... and I'm not "changing" anyhting... just randomly clicking images placed on a page... and within a couple clicks Dreamweaver has become so slow to "follow" my random clicks that it starts moving my images around -- in other words, it reaches a point where it's recognized the down-click but not the up-click of the mouse and is therefore 'moving' images rather than just selecting the different images.
By the way -- the "Properties" update in Dreamweaver has ALWAYS been horrific. If I'm updating links to a bunch of images I sometimes have to click an image three times to get the "Properties" tab to actually update. This is not a new problem... been around for as long as I was forced to ditch GoLive.
Back to the issue at hand... I have a page that has "SpryMenuBar.js" and "AC_RunActiveContent.js" and "SpryMenuHorizontal.css". That's pretty much it (except for inline css). My page contains a LOT of tables --- and a good number of tables nested in tables. There are also about 27 iFrames on the page (all pulling in clocks or countdown timers).
When I go from "Design" to "Split" or "Code" mode... there is only a 10-15 second wait. If, however, I'm unfortunate to have to change even one character of code and switch back to "Design" view.... I'm lucky if I only have to wait 20 seconds for Dreamweaver to become responsive again. The beach ball of death spins and spins and the "tool tip" for the cursor (which is a beach ball) flickers and flickers until Dreamweaver finally becomes responsive again -- almost as if Dreamweaver is re-reading the entire code and re-rendering the entire page extremely slowly each and every time I enter/exit code view.
If I'm in "Code" view I can make any changes I want... and there are no problems, no lags, no slowdowns. The beach ball of death only happens when I go back to "Design" view.
If, however, I'm in "Split" view... then I will get the Beach Ball of death after every confirmed change I make to the code.
When I'm only in "Design" view... I can pretty much leave my computer and go make a pot of coffee if I have the misfortune of having to copy and then paste a selected table, just as one example. Even the most minor of updates seem to cause problems. While in "Design" view only, I can click on an image... change the link for it... go to another image, change the link for it... but when I hit the third image... Beach Ball of Death. This doesn't always happen on the third image... sometimes it's the 4th or the 2nd or whatever... I'm just saying that it's not 100% of the time with every action I take.
Ever since updating to Mavericks this performance issue has been obvious with Dreamweaver CC (latest build Version 13.2 Build 6466). This problem is also obvious in Dreamweaver 6.
My current solution is to use Dreamweaver 5.5. It's a good thing I've been a loyal Adobe customer for as long as Adobe as been aquiring software -- and I still have all my old software. I would ditch any hopes of ever using Dreamweaver CC again, and still be perfectly happy, if it weren't for a few bugs in Dreamweaver 5.5 (such as the pick-whip going in the opposite direction of the screen when I try to pick-whip something from my "Files" tab, like when assigning a link to a graphic). Tiny oddities like that may make Dreamweaver 5.5 a bit of a pain to use for any real work... but for simply copy/paste and corrections on existing pages -- it operates at the speed I wish Dreamweaver CC could. Well... aside from the fact that the "Properties" tab has NEVER been able to update in real-time in any version of Dreamweaver... everything else works at the expected and desired speed.
So -- Dreamweaver 5.5 works. Dreamweaver 6 and Dreamweaver CC make me want to take up an art class or watch daytime television to kill the time I have to wait in-between clicks and code corrections and copy/pastes... waiting for that Beach Ball of Death to stop spinning.
By the way... when these "Beach Ball of Death" situations happen... the Activity Monitor shows Dreamweaver and WindowServer hitting some pretty high CPU loads for an extended period of time.
Please keep us posted if you find a solution. I've tried just about everything people have suggested on other threads and other boards... I've uninstalled Dreamweaver, reinstalled Dreamweaver... uninstalled Air and reinstalled Air... I've disabled all sorts of options like code assists and displaying external files and a bunch of other things... with no change at all in how Dreamweaver CC reacts.
I would really like to see a solution to this issue quickly, as it's been many months now. I've had no other problems with any of the other CC applications.
Have seen exactly what you are talking about.
In these forums there are many similar issues with different symptoms in different scenarios but it all boils down to the fact that since Maverick DWCC is now a tortoise .
You can ask me to delete and reset new preferences, quit and restart, remove js files and all the other standard type responses but at the end of the day I now drink a lot more coffee while waiting for DW to do stuff in a long time that used to be done as a matter of course.. I thank god every day that illustrator has not gone the same way.
We are internally aware of a bunch of performance issues & slowness in DW on Mac 10.9.x
We already had several connect sessions with users and observed the issue first-hand.
Hopefully, all this will be addressed in the next subsequent update. Rest assured, we are working diligently towards fixing them.
I have the same problem since a couple of weeks on my Mac Pro 12 cores 32 gig ram !?! I have disable the "Display styles"... a little better but still slow compare to the first version DW CC. Some times i have to switch to work in Coda or Edge Code.
Very time consuming the actual DW !!!
I'm waiting for this bug fix with my arm open...
How long must customers wait for an update? We are now forced to pay every month to use a product that never should have been released because it is unusable on a Mac. I've got a six-core Mac Pro running at 3.33 GHz with 48 GB of RAM and Dreamweaver is completely unusable. Scrolling is dreadful, typing even one word causes DW to churn. Trying to type a sentence takes tens of seconds.
Hello, Adobe, you take our money and treat us like slaves.
Yesterday I had a session with Adobe support (Subhadeep) where they verified that scrolling and typing stuttering make Dreamweaver unusable and it is not related to preference corruption. For users who must use DW (me, unfortunately), I discovered that the problem was somewhat diminished by resizing the DW window to make it smaller. But the problem is there in all screen sizes.
At some point Adobe is going to have to recognize that many of their software packages have turned into bloatware. Rather than spending their time figuring out how to permanently tap into users' pocketbooks, they need to get back to producing good software at good prices. The record over the last decade is not promising. Adobe purchases Framemaker, then kills it on the Mac. Adobe purchases Macromedia, then kills Freehand, a product that hands' down trounces Illustrator. Illustrator's user interface is so bad that that it makes me want to go back to pen and paper. Then there is the constant shifting of menu and submenu commands. Just when you learn where something can be found, Adobe moves it.
And the latest subscription-only debacle, which displays utter disdain for the needs of their customers. For more on the latter, see Thom Hogan's take: "The Fine Print in Adobe's Creative Cloud." When someone like that stands up to say it is wrong, Adobe would do well to listen.
A idea of when the update will be here would be good. These issues have been around way to long.
I'm trying to finish a simple 1 page list of size charts for a client and have only managed to edit 3 tables in 4hrs!
My hourly rate is $88 so I think Adobe owes me at least the next 6 months of CC at no charge.