I have had the following problem consistently used DW 12.1, as well as the version that was with CS 5.5. And I am almost sure it has something to do with the html or other code on my pages, but I thought a DW guru might help.
Basics First: DW 12.1 with the subscription. 64 bit Window 7.
Files that I am editing will periodically freeze, and then I get the "not responding" message above the menu bar. It freezes for 10 to 30 seconds (IT FEELS LIKE 10 TO 30 HOURS) and then starts working again.
Of course it only seems to happen when I'm on a roll making many duplicate mundane edits and then BOOM... can't do anything except shoot laser eye daggers at the screen and try to prevent myself from hyperventilating.
Here's the thing. I work on many sites; and this generally only happens on the site of my main client. I work off o local copies of the site, but I inherited them and they are massively full of bloat code, scripts, etc. I would not be surprised in the least if DW is trying to run or access some of this and this is the cause.
I turned off the "Display external files" option; are there other options I should try? It really is the absolute most annoying thing in my life right now (we should all be so lucky) and I'm hoping you might have a way to fix it.
I'd be happy to post code, but this page is a typical example where I might get the error 10 times in a 30 minutes while working on it...
Retard, (I know that sounds hilarious, but I don't know your name - no offense please! )
Like you said, if this happens only primarily on one of the many sites, it generally comes down to the type of code on that site.
And after looking at the URL you posted, seems like that page uses a lot of external references - JS and CSS.
Especially the last few lines:
Also, a couple CSS, JS references in the <head> section.
'Display External Files' only disables showing external files - but still loads them.
Can you try removing the external references and try working with the webpage in DW for a few minutes to see if the same problem persists? If it does, we know what was causing your issue.
Also, run your site through W3 validator to check and resolve errors: http://validator.w3.org/check?uri=http%3A%2F%2Fwww.healthfirst.com%2Fa cls-kit.html&charset=%28detect+automatically%29&doctype=Inline&group=0
Let us know how it goes.
One more suggestion - if the code is static but you're referencing it online, have you considered creating a local copy of the file? You could probably even use the local copy while staging on your computer - when you're putting it online, you could revert to a CDN hosted source - if you think that is necessary?
Thank you for the awesome and specific advice. I will try them out. (and I've got to stop picking my user names when I'm drunk... )
I thought the code I was referencing WAS local, but I now realize that you're right; I'll try a local version and see if that helps...
Thanks again for the advice; I'll try it out and see how things go...