Instant Dreamweaver Killer??

Report · Oct 29, 2007

Anyone get the same thing? I paste this code into a doc and DW CS3 build 3481 on Win XP just dies instantly.

Here's the code....

Report · Oct 29, 2007

PeteTheBloke wrote:
> Anyone get the same thing? I paste this code into a doc and DW CS3 build 3481
> on Win XP just dies instantly.

Yes, I can confirm it. Someone else reported a similar problem over the
weekend. With your code example, I can confirm that putting PHP code in
a select or option tag seems to cause CS3 to crash. The same code is
fine in Dreamweaver 8.0.2. Very weird.

--
David Powers, Adobe Community Expert
Author, "The Essential Guide to Dreamweaver CS3" (friends of ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/

Report · Oct 29, 2007

Well thanks for confirming it David. I'm sure I use similar code to this all the time with no previous problems. After all, it's the kind of snippet you reel off regularly in dynamic sites. It's frustrating when you open a file and forget it's there because DW just keels over.

Report · Oct 29, 2007

David:

I just tried this code from a post in the DW forum -

<html>
<head>
</head>
<body>
<form id="form1" name="form1" method="post" action="">
<select name="select" id="select">
<?php
?>
</select>
</form>
</body>
</html>

and it doesn't crash my CS3.

--
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
==================

"David Powers" <david@example.com> wrote in message
news:fg4ccf$l96$1@forums.macromedia.com...
> PeteTheBloke wrote:
>> Anyone get the same thing? I paste this code into a doc and DW CS3 build
>> 3481 on Win XP just dies instantly.
>
> Yes, I can confirm it. Someone else reported a similar problem over the
> weekend. With your code example, I can confirm that putting PHP code in a
> select or option tag seems to cause CS3 to crash. The same code is fine in
> Dreamweaver 8.0.2. Very weird.
>
> --
> David Powers, Adobe Community Expert
> Author, "The Essential Guide to Dreamweaver CS3" (friends of ED)
> Author, "PHP Solutions" (friends of ED)
> http://foundationphp.com/

Report · Oct 29, 2007

Murray *ACE* wrote:
> I just tried this code from a post in the DW forum -
>
> and it doesn't crash my CS3.

Murray, if you look at some of the crash threads, you'll see that some
people are reporting that the issue is resolved by turning the computer
clock back to before the weekend. I have tested several of these crash
reports on both XP and Vista. They always crash. That prompted me to
open the files from Chapter 11 of my "Essential Guide to CS3". They also
crash. They most definitely didn't crash when I developed and tested
them earlier in the year.

This prompted me to open the same files in Mac OS X 10.5. They don't crash.

What appears to be the common feature? Windows, plus the fact that the
clocks went back in Europe over the weekend. Why doesn't it affect you?
The one clear difference is that you're in the USA, which is no longer
in sync with Europe on daylight saving time. I suspect that if you
changed your computer's time zone to a European one, you might
experience the same results. What is odd is that this doesn't affect DW
8.0.2. The crashes occur only in CS3 on Windows.

I have sent a private email to a couple of senior members of the DW team
asking them to get on this case ASAP. There are just too many reports of
crashes for it to be a coincidence.

--
David Powers, Adobe Community Expert
Author, "The Essential Guide to Dreamweaver CS3" (friends of ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/

Report · Oct 29, 2007

I have come to the same conclusion, David. It was only on reading the last
post regarding this that I realized Europe and US are not on the same time
schedule.

It's a strange one, indeed.

--
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
==================

"David Powers" <david@example.com> wrote in message
news:fg4gik$qb4$1@forums.macromedia.com...
> Murray *ACE* wrote:
>> I just tried this code from a post in the DW forum -
>>
>> and it doesn't crash my CS3.
>
> Murray, if you look at some of the crash threads, you'll see that some
> people are reporting that the issue is resolved by turning the computer
> clock back to before the weekend. I have tested several of these crash
> reports on both XP and Vista. They always crash. That prompted me to open
> the files from Chapter 11 of my "Essential Guide to CS3". They also crash.
> They most definitely didn't crash when I developed and tested them earlier
> in the year.
>
> This prompted me to open the same files in Mac OS X 10.5. They don't
> crash.
>
> What appears to be the common feature? Windows, plus the fact that the
> clocks went back in Europe over the weekend. Why doesn't it affect you?
> The one clear difference is that you're in the USA, which is no longer in
> sync with Europe on daylight saving time. I suspect that if you changed
> your computer's time zone to a European one, you might experience the same
> results. What is odd is that this doesn't affect DW 8.0.2. The crashes
> occur only in CS3 on Windows.
>
> I have sent a private email to a couple of senior members of the DW team
> asking them to get on this case ASAP. There are just too many reports of
> crashes for it to be a coincidence.
>
> --
> David Powers, Adobe Community Expert
> Author, "The Essential Guide to Dreamweaver CS3" (friends of ED)
> Author, "PHP Solutions" (friends of ED)
> http://foundationphp.com/

Report · Oct 30, 2007

Please fix this by
1. Closing Dreamweaver
2. Set your clock to the correct time if it isn't already so
3. delete WinFileCache*.dat from
C:\Documents and Settings\[Your username]\Application Data\Adobe\Dreamweaver 9\Configuration
4. Start Dreamweaver and use it as usually
Thanks

Report · Oct 30, 2007

Thanks. That's great.

Report · Nov 05, 2007

quote:

Originally posted by: Marius Andreiana

3. delete WinFileCache*.dat from
C:\Documents and Settings\[Your username]\Application Data\Adobe\Dreamweaver 9\Configuration

Hi, small Problem:
I have installed DW on my desktop and on the laptop.
While the file exists on the desktop (and after deleting it DW works fine) on my laptop there is NO such file and NO such directory. So DW still crashes.
A allready searched for a file named as above, but no file was found....

Any glue?
Any help?

Thanks

Report · Nov 05, 2007

WebZopp wrote:
> on
> my laptop there is NO such file and NO such directory.

Start > My Computer > Tools > Folder Options > View. Make sure that Show
hidden files and folders is selected.

--
David Powers, Adobe Community Expert
Author, "The Essential Guide to Dreamweaver CS3" (friends of ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/

Report · Nov 08, 2007

quote:

Originally posted by: Marius Andreiana
Please fix this by
1. Closing Dreamweaver
2. Set your clock to the correct time if it isn't already so
3. delete WinFileCache*.dat from
C:\Documents and Settings\[Your username]\Application Data\Adobe\Dreamweaver 9\Configuration
4. Start Dreamweaver and use it as usually
Thanks

I've spent hours tracking the crash problem, so nice to know. But I would like to know if its because a update, if so, why nobody inform the solution to your registered customers?

Report · Nov 08, 2007

Thanks for the fix and the effort it took to figure it out.
I was experiencing the same thing with DW CS3 with CF code in select elements.
I am posting this on Nov 8, 2007 and am really disappointed in Adobe for not having issued an automatic update / fix, or at least posted an updater or a solution in the support areas. Sure get enough updates for other CS3 products.
Maybe they are sucking too much AIR to be bothered?

Report · Nov 09, 2007

hatethisnamegame wrote:
> I am posting this on Nov 8, 2007 and am really disappointed in Adobe for not
> having issued an automatic update / fix, or at least posted an updater or a
> solution in the support areas.

This issue first came to light after clocks in Europe switched from
summer time to winter time on 28 October. I alerted the Dreamweaver team
to mysterious crashes involving PHP. Within 36 hours, with the help of
many people in this forum and expert advice from the development team,
the solution was worked out. It was posted widely on this forum, and I
blogged about it to get the information out to as many people as possible.

In the meantime, Adobe investigated further; and with the help of
scripts provided by people who experienced crashes, one of the quality
engineers, David Alcala, managed to reproduce the problem. This led to
the publication of a technical note, which was widely publicized:

http://www.adobe.com/go/kb402776

The technical note refers only to PHP and ASP, but it appears that some
ColdFusion users have also been affected.

The problem exists only on Windows, and is triggered by the automatic
change to the computer clock at the end of summer time. Although it's
impossible to say with any certainty, it appears that the clock change
in Windows corrupts a cache file in Dreamweaver. No update has been
issued because the cache file is unique to each user. Clearing the cache
by deleting it solves the problem.

I'm sorry it's taken you so long to find the fix, but this issue and its
solution have been widely discussed in these forums over the past couple
of weeks. The technical note I referred to also comes up if you search
for "crash" in the Dreamweaver Knowledgebase.

--
David Powers, Adobe Community Expert
Author, "The Essential Guide to Dreamweaver CS3" (friends of ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/

Report · Nov 09, 2007

I believe that there was a potential fix posted within 24 hours of the issue
being raised.

--
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
==================

"David Powers" <david@example.com> wrote in message
news:fh1ccc$7u3$1@forums.macromedia.com...
> hatethisnamegame wrote:
>> I am posting this on Nov 8, 2007 and am really disappointed in Adobe for
>> not having issued an automatic update / fix, or at least posted an
>> updater or a solution in the support areas.
>
> This issue first came to light after clocks in Europe switched from summer
> time to winter time on 28 October. I alerted the Dreamweaver team to
> mysterious crashes involving PHP. Within 36 hours, with the help of many
> people in this forum and expert advice from the development team, the
> solution was worked out. It was posted widely on this forum, and I blogged
> about it to get the information out to as many people as possible.
>
> In the meantime, Adobe investigated further; and with the help of scripts
> provided by people who experienced crashes, one of the quality engineers,
> David Alcala, managed to reproduce the problem. This led to the
> publication of a technical note, which was widely publicized:
>
> http://www.adobe.com/go/kb402776
>
> The technical note refers only to PHP and ASP, but it appears that some
> ColdFusion users have also been affected.
>
> The problem exists only on Windows, and is triggered by the automatic
> change to the computer clock at the end of summer time. Although it's
> impossible to say with any certainty, it appears that the clock change in
> Windows corrupts a cache file in Dreamweaver. No update has been issued
> because the cache file is unique to each user. Clearing the cache by
> deleting it solves the problem.
>
> I'm sorry it's taken you so long to find the fix, but this issue and its
> solution have been widely discussed in these forums over the past couple
> of weeks. The technical note I referred to also comes up if you search for
> "crash" in the Dreamweaver Knowledgebase.
>
> --
> David Powers, Adobe Community Expert
> Author, "The Essential Guide to Dreamweaver CS3" (friends of ED)
> Author, "PHP Solutions" (friends of ED)
> http://foundationphp.com/

Report · Nov 09, 2007

Murray *ACE* wrote:
> I believe that there was a potential fix posted within 24 hours of the
> issue being raised.
>

From watching the forum over the last couple of weeks it would appear
that the fix wasn't that easy to find. I have just looked at the Support
site, and think that whilst having the "Hot Issues" on the support home
page is great, maybe they should do the same with the Dreamweaver
support page. It does have Top Issues listed, but the latest is 19 Apr
07. What it needs is a new box with issues like the one we have just
experienced.

What is weird is that I have not experienced this issue and I am based
in the UK. I have worked on dynamic select lists without any problems.

Steve

Report · Nov 09, 2007

Murray *ACE* wrote:
> I believe that there was a potential fix posted within 24 hours of the
> issue being raised.

I'm afraid you're mistaken, Murray. I raised the issue internally with
Adobe at 11.40 GMT on 28 October. The potential fix (which turned out to
be the real solution) was confirmed at 18.01 GMT on 29 October and
subsequently posted here. That's a gap of more than 30 hours, which is
why I said "within 36 hours". However, there's little point quibbling
about exactly how long it took. Considering the time difference between
California and Europe, and that it was first raised on a Sunday, it was
fixed very quickly.

The real problem is that, in spite of many people's efforts, getting the
message to everyone affected has been difficult. As Steve (Dooza) notes,
it's not listed anywhere on the Dreamweaver support page as a "Hot
issue". There does need to be a better system for propagating
information about this sort of problem.

--
David Powers, Adobe Community Expert
Author, "The Essential Guide to Dreamweaver CS3" (friends of ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/

Report · Nov 09, 2007

>There does need to be a better system for propagating information about
>this sort of problem.

Certainly agree with that. It's curious indeed that this issue didn't arise
with the US time change, however....

--
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
==================

"David Powers" <david@example.com> wrote in message
news:fh1t1m$svc$1@forums.macromedia.com...
> Murray *ACE* wrote:
>> I believe that there was a potential fix posted within 24 hours of the
>> issue being raised.
>
> I'm afraid you're mistaken, Murray. I raised the issue internally with
> Adobe at 11.40 GMT on 28 October. The potential fix (which turned out to
> be the real solution) was confirmed at 18.01 GMT on 29 October and
> subsequently posted here. That's a gap of more than 30 hours, which is why
> I said "within 36 hours". However, there's little point quibbling about
> exactly how long it took. Considering the time difference between
> California and Europe, and that it was first raised on a Sunday, it was
> fixed very quickly.
>
> The real problem is that, in spite of many people's efforts, getting the
> message to everyone affected has been difficult. As Steve (Dooza) notes,
> it's not listed anywhere on the Dreamweaver support page as a "Hot issue".
> There does need to be a better system for propagating information about
> this sort of problem.
>
> --
> David Powers, Adobe Community Expert
> Author, "The Essential Guide to Dreamweaver CS3" (friends of ED)
> Author, "PHP Solutions" (friends of ED)
> http://foundationphp.com/

Report · Nov 09, 2007

Murray *ACE* wrote:
> Certainly agree with that. It's curious indeed that this issue didn't
> arise with the US time change, however....

It did. The problem is that it doesn't appear to have affected everyone.
David Alcala at Adobe has been investigating this issue since it was
first reported. He has managed to reproduce it with PHP, but not with
ASP or ColdFusion. However, quite a lot of ASP and ColdFusion users have
reported suffering from it. But in all cases that I have heard of,
deleting WinFileCache-********.dat fixes the problem.

I've heard of at least one person who was still working in Dreamweaver
at the time of the clock change, and who has suffered no crashes. I know
that, in the past, you have left Dreamweaver running for days without
switching off. If your computer was running with Dreamweaver open at the
time of the clock change, that might explain why you escaped.

--
David Powers, Adobe Community Expert
Author, "The Essential Guide to Dreamweaver CS3" (friends of ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/

Report · Nov 09, 2007

On Fri, 09 Nov 2007 16:12:07 +0000, David Powers <david@example.com>
wrote:

>Murray *ACE* wrote:
>> Certainly agree with that. It's curious indeed that this issue didn't
>> arise with the US time change, however....
>
>It did. The problem is that it doesn't appear to have affected everyone.
>David Alcala at Adobe has been investigating this issue since it was
>first reported. He has managed to reproduce it with PHP, but not with
>ASP or ColdFusion. However, quite a lot of ASP and ColdFusion users have
>reported suffering from it. But in all cases that I have heard of,
>deleting WinFileCache-********.dat fixes the problem.
>
>I've heard of at least one person who was still working in Dreamweaver
>at the time of the clock change, and who has suffered no crashes. I know
>that, in the past, you have left Dreamweaver running for days without
>switching off. If your computer was running with Dreamweaver open at the
>time of the clock change, that might explain why you escaped.

Is it at all possible that those who were not affected are those who
in Vista have UAC turned off, or in XP installed as the administrator
(rather than using another account with admin privileges)?

Unlike Murray, I don't keep DW running for days. Like Murray, I
turned UAC off in Vista before installing (and continue to keep it
turned off). Also like Murray, I didn't experience a crash.

My thinking is this has something to do with Windows and permissions.

Win
--
Win Day, Wild Rose Websites
http://www.wildrosewebsites.com
winday@NOSPAMwildrosewebsites.com
Skype winifredday

Report · Nov 09, 2007

I don't think it was open at the time of the clock change.

--
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
==================

"David Powers" <david@example.com> wrote in message
news:fh20ua$4qi$1@forums.macromedia.com...
> Murray *ACE* wrote:
>> Certainly agree with that. It's curious indeed that this issue didn't
>> arise with the US time change, however....
>
> It did. The problem is that it doesn't appear to have affected everyone.
> David Alcala at Adobe has been investigating this issue since it was first
> reported. He has managed to reproduce it with PHP, but not with ASP or
> ColdFusion. However, quite a lot of ASP and ColdFusion users have reported
> suffering from it. But in all cases that I have heard of, deleting
> WinFileCache-********.dat fixes the problem.
>
> I've heard of at least one person who was still working in Dreamweaver at
> the time of the clock change, and who has suffered no crashes. I know
> that, in the past, you have left Dreamweaver running for days without
> switching off. If your computer was running with Dreamweaver open at the
> time of the clock change, that might explain why you escaped.
>
> --
> David Powers, Adobe Community Expert
> Author, "The Essential Guide to Dreamweaver CS3" (friends of ED)
> Author, "PHP Solutions" (friends of ED)
> http://foundationphp.com/

Report · Nov 09, 2007

Could be. I do have it turned off....

--
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
==================

"Win Day" <winday@NOSPAMwildrosewebsites.com> wrote in message
news:fa29j3lqj7j53jo8f66vntb3cqnvnkqb42@4ax.com...
> On Fri, 09 Nov 2007 16:12:07 +0000, David Powers <david@example.com>
> wrote:
>
>>Murray *ACE* wrote:
>>> Certainly agree with that. It's curious indeed that this issue didn't
>>> arise with the US time change, however....
>>
>>It did. The problem is that it doesn't appear to have affected everyone.
>>David Alcala at Adobe has been investigating this issue since it was
>>first reported. He has managed to reproduce it with PHP, but not with
>>ASP or ColdFusion. However, quite a lot of ASP and ColdFusion users have
>>reported suffering from it. But in all cases that I have heard of,
>>deleting WinFileCache-********.dat fixes the problem.
>>
>>I've heard of at least one person who was still working in Dreamweaver
>>at the time of the clock change, and who has suffered no crashes. I know
>>that, in the past, you have left Dreamweaver running for days without
>>switching off. If your computer was running with Dreamweaver open at the
>>time of the clock change, that might explain why you escaped.
>
>
> Is it at all possible that those who were not affected are those who
> in Vista have UAC turned off, or in XP installed as the administrator
> (rather than using another account with admin privileges)?
>
> Unlike Murray, I don't keep DW running for days. Like Murray, I
> turned UAC off in Vista before installing (and continue to keep it
> turned off). Also like Murray, I didn't experience a crash.
>
> My thinking is this has something to do with Windows and permissions.
>
> Win
> --
> Win Day, Wild Rose Websites
> http://www.wildrosewebsites.com
> winday@NOSPAMwildrosewebsites.com
> Skype winifredday

Report · Nov 09, 2007

On Fri, 9 Nov 2007 12:31:58 -0500, "Murray *ACE*"
<forums@HAHAgreat-web-sights.com> wrote:

>Could be. I do have it turned off....

Me too. That's what made me think of it.

Win
--
Win Day, Wild Rose Websites
http://www.wildrosewebsites.com
winday@NOSPAMwildrosewebsites.com
Skype winifredday

Report · Nov 05, 2008

This issue seems to have reared its head again this week. Surely a year would have been long enough to fix it? If I left my clients waiting a year for a bug fixes I'd be bankrupt.

Report · Nov 06, 2008

I hope I do not have to keep deleting this file each time DW crashes.

Is this a one off or just a daylight savings problem?

Report · Nov 07, 2008

Seems you have to do it every time the clocks go back 🙂 Each year it'll get easier to remember.

Makes you wonder what the file is for in the first place. I didn't notice DW suffering for its loss. Maybe I'll write an extra line in my cookie-deleting batch file and just delete it every night.

Instant Dreamweaver Killer??

1 Correct answer