Dreamweaver CS6 - Always 100% CPU

[shdskj_gfd]

Hi,

I've just installed the trial of Dreamweaver CS6. And I noticed it's always taking 100% of the CPU!!

I disabled RELATED FILES, deleted the cache, but it still takes 100% of the CPU.

The CPU goes down to 0% once I enter any menu in Dreamweaver.

I tried all the solution offered here: http://forums.adobe.com/thread/656747 but it still didn't helped.

Any advice?

Thanks!

[Janaki Lakshmikanthan]

Thanks for sharing the test files!

We could reproduce this issue locally and we are investigating on it. We will keep you posted on this sooner.

Regards,

Janaki

[strassenkehrer]

Hi Preran,

can you tell me when the update will be available in German language? I'm using CS6 Master Collection

Now, I have find out, that if I open a javascript-document the first time, the CPU goes to 50 % usage, if I close the document, nothing changes (50% usage) and if I open it again, the usage will grown to 100 %

My Computer:

Intel i7 2620M

3GB DDR3

480GB SSD

1280 x 800

Windows 7 Ultimate 64 bit

best regards

Kai

[Janaki Lakshmikanthan]

Hello All,

High CPU usage in Code view issue has been resolved for Mac and the new build 12.0.3 is available for update for Non-Creative Cloud Members too. Please update to the latest build.

In Dreamweaver use menu 'Help' > Updates to get the latest build 12.0.3

The above update is available for both Windows and Mac.

Off topic: Creative Cloud users too have an update 12.1.1 to continue using Phone Gap from DW.

Regards,

Janaki

[Prussian77]

Janiki,

I have downloaded a 30 day trial version of Dreamweaver CS6. I was updated to version 12.0, and it was fine. Adobe asked if I wished to update to 12.0.3 and I said yes. Now I am having the 100%CPU usage problem that others have described. When Dreamweaver first opens, I have 13-15% CPU usage. But when I go to open a file in DW, everything stops and CPU hits (and stays at) 100% for 2 or 3 minutes before opening whatever file I was atempting to open. Afterwords it drops back down to the 13%CPU, but when I go to open a menu item (ex. Insert) it jumps back up. Please help, because it is making DW unusable for me.

-Dimitri

[BenPleysier]

Even 13-15% is much too high for a stationary program, this should be no more than 0.5%

Click on a menu item to show the drop-down and see how the CPU usage decreases.

[Prussian77]

When I click a drop down menu (such as the "Insert" or "File") CPU increases to 100% and stays there for at least 2-3 minutes, then it drops down to 5-13% and does whatever it is I wanted it to do in the first place.

-Dimitri

[magretz]

I'm having the exact same issues. I'm running windows10 x86 dual-core and Dreamweaver eats up an entire core while just sitting there with no files open.

Any help would be greatly appreciated!!!

[strassenkehrer]

Today Dreamweaver made an automatical update, but my machine consumes always more than 50% CPU., if I'm opening a javascript-file. After I close it and reopen it again, the conspumtions increase to 100 % CPU. So nothing changed since the update.

What should I do now?

My Dreamweaver-Version is: 12.0 Build 5861...

Regards

Kai.

P.S: I saw in my last post was a mistake: 8GB DDR3...

[Guest]

STILL happening to me and quite regularly:

Date/Time:       2013-04-19 16:09:44 -0400

OS Version:      10.8.3 (Build 12D78)

Architecture:    x86_64

Report Version:  11

Command:         Dreamweaver

Path:            /Applications/Adobe Dreamweaver CS6/Adobe Dreamweaver CS6.app/Contents/MacOS/Dreamweaver

Version:         12.0.3.5861 (12.0.3)

Parent:          launchd [269]

PID:             47512

Event:           hang

Duration:        0.90s

Steps:           10 (100ms sampling interval)

Hardware model:  MacPro3,1

Active cpus:     8

Free pages:      798926 pages (-1923)

Pageins:         1 pages

Pageouts:        0 pages

Process:         Dreamweaver [47512]

Path:            /Applications/Adobe Dreamweaver CS6/Adobe Dreamweaver CS6.app/Contents/MacOS/Dreamweaver

Architecture:    i386

Parent:          launchd [269]

UID:             501

Task size:       74908 pages (+1)

CPU Time:        0.812s

  Thread 0x1b290f   priority <multiple> cpu time   0.812s

  10 start + 53 (Dreamweaver) [0x4e1175]

    10 main + 95 (Dreamweaver) [0x113069f]

      10 CWinAppImpl::Run() + 36 (Dreamweaver) [0x11303b0]

        10 CRealApp::Run() + 395 (Dreamweaver) [0x114cb4f]

          10 exo::app::OS_AppBase::RunEventLoop() + 67 (exo) [0x4103b73]

            10 -[NSApplication run] + 855 (AppKit) [0x988d163c]

              10 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 119 (AppKit) [0x988db1dc]

                10 _DPSNextEvent + 724 (AppKit) [0x988db9aa]

                  10 BlockUntilNextEventMatchingListInMode + 88 (HIToolbox) [0x924cbb44]

                    10 ReceiveNextEventCommon + 162 (HIToolbox) [0x924cbbf5]

                      10 RunCurrentEventLoopInMode + 242 (HIToolbox) [0x924cbf5a]

                        10 CFRunLoopRunInMode + 123 (CoreFoundation) [0x95b51e9b]

                          10 CFRunLoopRunSpecific + 378 (CoreFoundation) [0x95b5202a]

                            10 __CFRunLoopRun + 2154 (CoreFoundation) [0x95b52cfa]

                              10 __CFRunLoopDoSource1 + 146 (CoreFoundation) [0x95b1cf62]

                                10 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 53 (CoreFoundation) [0x95b1d335]

                                  10 mshMIGPerform + 504 (HIServices) [0x9004cff7]

                                    10 _XCopyAttributeValue + 374 (HIServices) [0x90073d70]

                                      10 _AXXMIGCopyAttributeValue + 251 (HIServices) [0x9006cd28]

                                        10 CopyAttributeValue + 349 (AppKit) [0x98b144fd]

                                          10 CopyCarbonUIElementAttributeValue + 60 (AppKit) [0x98b17cc7]

                                            10 CarbonCopyAttributeValueCallback(__CFData const*, unsigned long, __CFString const*, void const**, void*) + 83 (HIToolbox) [0x924fd598]

                                              10 HLTBCopyUIElementAttributeValue + 64 (HIToolbox) [0x924fb23e]

                                                10 Accessible::GetNamedAttributeData(__CFString const*, void const*, void const**, unsigned char*) + 171 (HIToolbox) [0x924fb34d]

                                                  10 Accessible::SendEvent(OpaqueEventRef*, bool) const + 105 (HIToolbox) [0x924fbe9d]

                                                    10 SendEventToEventTargetWithOptions + 94 (HIToolbox) [0x924a75ca]

                                                      10 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 430 (HIToolbox) [0x924a7780]

                                                        10 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1343 (HIToolbox) [0x924a8394]

                                                          10 _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36 (HIToolbox) [0x926209bb]

                                                            10 HIObject::EventH

[Guest]

Hi,

I have DW CS6 with CPU usage 50% on it. It drops down for example when i use File->New or insert->Image. When i am in any kind of menu it drops down to 0.1 or 0.0 %. When i back to my file without even doing nothing it goes up by itself to 50%.

I have installed windows 8.1 x64

[BenPleysier]

This thread is 2 years old and the solution has been given. Have a look at posts 43 and 44.

Good luck!

[JenniferAnnsGroup]

Post 52 shows that Adobe was able to recreate this problem. Unfortunately there's been no follow-up providing a solution.

And FYI: if Adobe tells us to update to a new version (or a cloud based version) that isn't much of a solution.

My nonprofit organization accepted Adobe's kind offer several years ago to purchase their suite of software at heavily discounted pricing. We've purchased three different suites which has provided us with their powerful software at a very affordable price and has helped us TREMENDOUSLY with our nonprofit mission. Adobe's support of nonprofit groups is commendable.

Unfortunately Dreamweaver has been a bit of a beast and right now I'm heavily reliant on using it.

The new versions are not affordable for us (even with Adobe's discount for nonprofit orgs the requirement to pay a fee in perpetuity just does not make sense for our very very small budget - it would be great if they once again made it available for a one-time purchase price as they used to).

So: upgrading or moving to the subscription service is not an option (at least not for my tiny NGO). What I need is for the product that I've legally purchased to work properly.

Post 52 from Adobe was made back in 2013. An update (with associated solution) would be appreciated.

Drew Crecente

Exec Director, Jennifer Ann's Group

[junl80729253]

I've been testing Dreamweaver CS6 on both Windows and Mac for several months, and have not encountered CPU problems on either system.

Obviously, that's not much help to you, but it sounds as though it's likely to be something specific to your system that's causing the spike. Adobe doesn't offer technical support for trial versions, but if you post more details of your operating system and specifications, it might help others narrow down the cause of the problem.