Skip to main content
lcg_2012
Inspiring
June 18, 2013
Question

Dreamweaver CC Crashes Constantly

  • June 18, 2013
  • 24 replies
  • 68336 views

Downloaded Dreamweaver CC last night. Cannot keep it open for more than a few seconds. Noticed if I open a file, no code shows in the Code Inspector. If I click the X to close the file, DW CC crashes. Think this release came a out a bit too soon. Buggy as hell.

This topic has been closed for replies.

24 replies

Richard Wilding
Participant
November 18, 2013

I've been using Dreamweaver for years and this CC version is terrible, It crashes constantly and typing in code view is so slow that it's unusable. This product should never have been released...

Participating Frequently
August 13, 2013

Yep, me too. It crashes about 75% of time I do anything.

- Upload files

- Save new files

- Find & Replace

- Copy & Paste

I am NOT using fluid grids, and my CSS files are perfect (no missing {s, etc.). I am using SASS for managing my CSS files, so you know they're not a problem or else I would get an error on save.

I take a chance with everything that I do in DW CC. I've been a DW user since version 1 with Macromedia and have never ever had problems like this.

I've tried all of the suggestions: font duplicates, removing configuration files, etc.

Participating Frequently
August 27, 2013

I REALLY want to be able to use Dreamweaver CC but it crashes all the time on me, too. I've also been given an unhelpful run around and literally conflicting answers by tech support, sales, and these boards.

I've spelunked in my libraries, been nice to Verdana, and searched for media query curly close quotes and I still crash. Often. A lot. All the time. SO MUCH I GET NOTHING DONE.

Thanks to S.E.O. it is difficult to find accurate, honest reviews and information about the CC products and that is sad. In fact it borders on dishonest. I agree with the voices saying these releases are too early and incomplete. When I buy software it is a tool I use to complete a job. The tool should not require as much time, effort, and attention as my job.

I am mac OS running 10.8.2 and am about 2 weeks into my CC membership and seriously considering canceling. What use are super duper features if they literally don't work? Is it more productive to crash 8-12+ times a day or just teach my self to hard code media queries?

Janaki Lakshmikanthan
Adobe Employee
Adobe Employee
August 27, 2013

Hi,

Please update to the latest version of Dreamweaver CC 13.1 which has got lot of bug fixes (fixes for crashes too) and lot more improvements. You could use menu Help > Updates from Dreamweaver application or use Creative Cloud application and download the latest patch for DW CC. Use may refer this link for more details http://forums.adobe.com/message/5630415#5630415

Regards,

Janaki L

Known Participant
July 6, 2013

Dreamweaver CC is very buggy, crashes all the time - trying a number of different settings. Certainly having Dreamweaver and Photoshop together makes the whole thing very flaky (CS6 Photoshop and DW were fine). Not using any of the amazing new features in DMW, the code is fairly basic stuff.

Participant
July 9, 2013

I was having constant crashes as well. I opened FontBook and had a TON of duplicates. I resolved my duplicates and all seems to be fine…for now. We'll see how the day goes.

hyadav
Adobe Employee
Adobe Employee
June 18, 2013

Try removing the files listed below along with those mentioned above to your desktop.

1) /Users/Your User Name/Library/Preferences/com.adobe.dreamweaver-13.0.plist

2) /Users/Your User Name/Library/Preferences/com.adobe.dreamweaver-13.0.plist.lockfile

3) /Users/Your User Name/Library/Caches/com.adobe.dreamweaver-13.0

Restart your computer and Launch DW.

-Harshit yadav

Legend
June 18, 2013

hyadav wrote:

-Harshit yadav

Yes. that's what most people are saying at the moment, lol

Preran
Community Manager
Community Manager
June 18, 2013

I'm on Mac OS X Lion (10.7.5).

The steps outlined at the top of the thread didn't work for me until I created and saved a workspace.


Hi lcg_2012

This issue has been reported, and the team is looking into it. Will keep you posted. Sorry for the inconvenience.

Thanks,

Preran