Dreamweaver CS3 crashes and won’t start up again
Hey kids, this is definitely one of the weirdest bugs I have ever clapped eyes on.
Not for the first time, I was happily authoring CSS and Dreamweaver CS3 crashed. Turns out, it doesn’t have to be specifically CSS, but that was my situation anyway.
The crash
It’s all too familiar: this is DW after all, and those of us who have used it from the start will know the pedigree. But I try to restart the program anyway: it’s 1am and I don’t need this. Nope, fail. Dreamweaver CS3 won’t start on Windows XP. In these times of quad processors and 32-bit colour, has the long-exorcised ghost of DW’s buggy past returned to haunt us?
The following options were available:
- Abuse someone at Adobe
- Reinstall Dreamweaver
- Try to clean out the config files so that Dreamweaver has to create new ones on restart (an old and occasionally successful solution)
And the answer? None of the above.
The fix turned out to be simple, though somewhat obscure. I shall elaborate in a moment, but first I must attribute my source. In August 2007, Adobe Community Expert and author David Powers sussed out this profoundly ugly problem in the Macromedia.Dreamweaver Google Group. At the time, it was undocumented elsewhere and not particularly easy to find with bland keywords in search engines.
The cause of the crash
Apparently, an install of Dreamweaver CS3 (mine is currently v9.0 Build 3481) crashes if you edit a file to exactly a multiple of 8,192 bytes. Not a byte more, not a byte less. The chances of this happening are probably fairly small: to edit a file to the exact size at the same moment that DW does some processing and gets upset.
Don’t believe me? I wouldn’t have either in your position. But here’s what happened: I’m editing a document of any supported format, I’m just about to change a particular value and suddenly it crashes. So I checked out David’s comment above and, lo and behold:
So now what?
If you have this bug, from here it’s quick and easy to escape. Don’t bother trying to do anything with Dreamweaver CS3 because as long as your file is a multiple of 8,192 bytes, you ain’t going nowhere.
Step 1. If you were working within a Site, you can test if this bug was behind the crash
If you were editing your file within a defined Site, read on. Otherwise, you can skip to 2.
In Windows Explorer, temporarily rename the folder that contains your Site, so that Dreamweaver CS3 starts successfully, asking you to Manage Sites… because of course it can’t find your original folder.
If you were to point Manage Sites… to the new folder name, Dreamweaver CS3 would crash again, so just exit the app for now. You can now be pretty sure you’ve encountered this filesize bug.
If DW doesn’t start properly after this step, then you have some other problem and I’m sorry your visit here didn’t help.
Step 2. Edit the file that caused the crash outside of Dreamweaver CS3
Next, in a different text editor such as Notepad, increase the filesize of the file that you were editing when DW crashed – just by adding a bit of whitespace, for example – and then resave it. You could also decrease the file size by deleting whitespace, but of course you risk repeating the bug when you work on the file again later or indeed, you might not have anything to safely delete, so I’d recommend increasing instead.
Now, having altered the file, be sure to check that your filesize is indeed no longer a multiple of 8,192kb.
If you were working within a Site as described in Step 1, you can now rename the folder of your Site back to its original name in Windows Explorer.
Restart Dreamweaver CS3 and you should be back in action. I hope it worked for you too!
Afterthought
As you can probably see, there are quite a few satisfied customers in the Responses below, from Denmark to Chile. So why not let me know if you had this problem too and if your situation was a little different, please add to the knowledge.
And finally, this incident jogged my memory of another oddball software behaviour I encountered once in the early days of Office 2007 for Windows, because it too was about processing bytes and coming out with the wrong result. Check out this anomaly with Excel 2007: if you multiply 850 by 77.1 you get 100,000. The real answer? 65,535 of course, a juicy, meaningful number for aficionados of binary computing! [15 April 2008: I tested this again recently and it appears to have been patched - Mike]
Comments
320 responses so far to Dreamweaver CS3 crashes and won’t start up again
Why not give me your comments?
See also:
Macromedia.com metamorphosis
Change is finally happening over at macromedia.com, with the Adobe visual identity steadily (if clumsily) getting to grips with the Macromedia site structure. It remains to be seen whether Macromedia’s traditionally ...
- Originally published: 8 Dec 2005 in Technology
Solution to nested DIV float problems
This item is now out of date. See the updated version. I recently discovered a CSS hack that has come in very handy indeed since. The problem arises in both Firefox and ...
- Originally published: 12 Sep 2005 in Technical
IE7 only: float bug on elements with italic, background properties
Setting font-style:italic in your CSS for elements in the vicinity of a floated element can actually trigger a float bug in Internet Explorer 7. This is only a problem, so far ...
- Originally published: 13 Jul 2009 in Technical
Macromedia releases Studio 8
Studio 8 is here, announced Macromedia on Monday. I’ve taken a look at the demos. A lot of the focus seems to have been on GUI improvements and extended support for ...
- Originally published: 10 Aug 2005 in Technology
RouteOne online: doing the BUSiness
The old RouteOne website A new website for RouteOne, the leading publication in the Coach and Bus industry, is set to go live shortly. My job was to turn the old offering ...
- Originally published: 9 Sep 2006 in Technology
Who is that guy?
Hello you. I'm Mike Padgett and I work in the technology sector as an Information Designer.
I also enjoy travel, concerts, films and walking.
I'm based in Brussels, Belgium. My current favourite Belgian beer is St Feuillien Brune.
April 7th, 2008 at 10:01
cheers Mike – worked a treat!
April 14th, 2008 at 23:36
All the resources on the internet, and I find this solution on page 3 of Google search results. This problem didn’t present so much of an inconvenience in CS2 because I was still using notepad interchangeably and must have fixed it without realizing it by using notepad. Now I’ve moved up to CS3 and am far more dependent on DW and couldn’t find my way past the constant crash. Thanks a million for posting this issue!
April 15th, 2008 at 11:23
[...] jeg faldt over dette indlæg på Mike Padgett’s blog. Løsningen var såre simpel. Dreamweaver CS3 har tilsyneladende en bug, der gør at den ikke kan [...]
April 15th, 2008 at 19:11
Thanks for your help. All of a sudden Dreamweaver CS3 just crashed and would not re-open. The intro screen would flash and then nothing would happen. I tried a restart to the computer to no avail. A quick Google search (man I love Google) and I was able to find several references, but most required an uninstall, wiping the registry, etc. I no longer have easy access to the install CD, being part of the corporate machine, so that was not an option. After reading this article, I found that my CSS file was exactly 8,192 bytes. I edited it with notepad, and voila…. Dreamweaver opened just fine.
Very weird bug.
April 15th, 2008 at 19:25
No worries, Chris, I’m happy that this has been helpful to you!
The credit really goes to David Powers as mentioned in the article, who figured this one out some time ago. As I have done in the past with obscure issues, I just wanted to add another voice out there because it took me so long myself to find a fix for this.
No patch yet from Adobe as far as I can see. Let’s hope they sort it. Meantime, if anyone can tell us if this issue occurs in DW8 or even earlier, or when editing other formats than CSS please let us know!
April 16th, 2008 at 15:58
OHMIGOD! That is possible the most ridiculous bug. This is the second time CS3 has bugged out on me, first time the licensing stopped working.
Thanks a million for this solution, was beginning to have feelings of doom about how bad this bug might be, phew.
April 25th, 2008 at 19:28
I am so glad I found your solution. I was just about to start uninstalling and reinstalling and who knows what else.
This probably saved me at least 4 hours of troubleshooting.
Thank you for posting this fix – what a weird bug.
Doug
April 30th, 2008 at 4:09
Amazing! I thought I had tried everything and this really saved the day. Thanks for the post.
May 4th, 2008 at 7:29
Mike,
I just wanted to say thanks for figuring this out first. I was really [word removed] because I’m on a super tight deadline and right when I’m almost completed with my work Dreamweaver decides to go “Capooy”! So I was like what the heck is going on here, and I’m actually on vista (unfortunately, we don’t work on apples at work) and I was like this must be another vista problem, great what do I do now! So I was just trying to do some basic trouble shooting and I realized that I could start because the caching in Dreamweaver would always stop half way through and I get the famous, this application has experienced and error yada yada…etc etc.
So I finally got DW started and I was like “is it my PHP code, did I do something wrong”. I hovered over the css file and “BAM!” that’s when DW stopped running. I spent all this time trying to figure this out and repaired my installation of DW…. all I had to do is search on google for CSS problem with crashing DW and there was my answer…I hate you. JK.
Anyways thanks for giving me a little light on this situation. I’m going to have to tell my colleagues at work to make sure you keep your CSS at a 8kb minimum, WTF is that adobe. Please fix this!
Thanks,
Brad
May 8th, 2008 at 13:17
Thank you so much. Mixed emotions here. From being fuming mad and getting ready to reinstall dreamweaver, to thrilled about such a simple fix, to angry for such a stupid bug, to amazement at how crazy this is!
Thanks SO much. Ever so grateful.
May 15th, 2008 at 17:56
Thanks Mike,
I took the trouble of reinstalling and then again going through google (may be firs time my wordings was not proper!) After browsing through a couple of pages I landed here! Yes my CSS file which I was just modifiying reached the magic mark of 8192! just some blank lines and a cooment line at bottom and saved the file. DW is back after giving me 24 hrs of headache! I have no words to praise you for this post! Keep up the good work of spreading the solutions even though they may available at some other forums, more the better! Thanks once again.
May 23rd, 2008 at 17:18
I had this problem a year or so ago, and resolved it with a series of steps that took some hours and at the time, was I mad … I am at a remote location and my notes weren’t here (turned out that was a good thing) … here comes the problem again … I searched for the solution and found THIS. I realized I had been working on css at the time so I thought, hmmm … first I checked the size of the file, and it was not exactly 8,192 bytes but I tried by using the steps anyway … and it WORKED. Back up and running in less than 5 minutes…. thank you, thank you, to you, David Powers et al. This is a bizarre bug.
May 24th, 2008 at 0:10
Yes, we have encountered this bug on a variety of sites.. Even worse, it happens on MULTIPLES of 8192 bytes. One site we had, the file was 16383 bytes (not 16384, though, which is weird), and it was crashing in the exact same manner.
Really weird that it still crashes even when one byte off, though.
Pretty harsh bug. Basically, Dreamweaver crashes if the filesize of your CSS file is within one byte of a multiple of 8192.
June 2nd, 2008 at 22:24
perfect, i was 1 dice roll away from total reformat of a pc that did not need a format that was 2.5 years old, saved me a lot of hassle, I tried a lot of things before searching for this solution. Yeee all de man!
June 6th, 2008 at 13:28
Incredible ! Only thing is – my .css file was 4.20KB’s and in the properties window said that size on disk is 8.192KB … Amazingly stupid bug … Thanks for this solution and inspired blog post .. ;)
June 7th, 2008 at 19:20
Thanks a lot, saved me a couple of hours!
> Even worse, it happens on MULTIPLES of 8192 bytes.
Absolutely true, DW crashed on my 24575 bytes CSS.
June 10th, 2008 at 3:44
What a lifesaver . . . thank you and thanks for those who mentioned the bug affecting multiples.
I can’t imagine the odds of this but I made an edit that sized my PHP file to 24,576 AND the linked style sheet to 16,384. I feel like I should have won something by hitting those odds but the fix in this post is enough of a prize for me. Thanks again.
June 10th, 2008 at 4:07
As an addendum to my prior comment, I encourage people who encounter this to report it to Adobe: http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
June 16th, 2008 at 8:51
Holy **** you are the man… What a load of bull****… I almost had to go Office Space on my PC…
June 18th, 2008 at 8:25
I just experienced this problem and did a quick google search and glad to have found your site. Thanks for putting this up.
June 19th, 2008 at 10:32
Crazy ****, thx for the solution Mike, you saved my day man! It really crashes on multiples of 8192, my file was 16.384 Bytes… so strange!
June 21st, 2008 at 15:47
Hi Mike and all,
Ok, Im having this problem but the thing here is I wasnt working on any CSS files. I was working on a html file, it got stuck, crashed and refused to start up now :( I tried uninstalling and re-installing, removing the config files and repairing and also changing the location of my site folder, renaming, but nothing works. Ive gone thru all the CSS files in the DW flder but nothing shows 8192kb…any idea what else I can do to get this prog to start, Thanks
June 22nd, 2008 at 10:43
If this bug is causing Dreamweaver CS3 to crash, the source of the problem will definitely be in the last file you were working on (your HTML file). The file format is not important.
Comments from this thread suggest that the bug causes a crash if the size of the file is 8,192 bytes, or multiples of that (so 4096, 16,384, 24,575, 32,768 … etc).
Hope this helps. If it doesn’t, you have a different issue.
June 22nd, 2008 at 19:44
Increible, agregue un par de lineas para alterar el tamaño del ultimo archivo css en que trabaje y listo, cargo de nuevo el DW.
Muchisimas gracias, ya habia tratado todo y estaba a punto de formatear el disco y reinstalar Vista.
Gracias!
June 28th, 2008 at 23:34
Incredible I got a css file that is 8.192KB … what a !#%* bug … Thanks for this solution and great post ;) Heel erg bedankt.
July 1st, 2008 at 0:49
Big thanks from me too, it’s 23:36 and I’ve got a website to deliver tomorrow. Would you believe it my CSS file hit 8192bytes and nothing worked! Thanks for the tip you’re a lifesaver!
July 2nd, 2008 at 7:28
Happened to me too..thank god for this blog post. It’s been a long day getting up to speed with Vista and I thought this was another Vista bug.
July 4th, 2008 at 0:06
you rock man!!!!! Saved our butts here. Thanks a million!!
July 4th, 2008 at 2:44
[...] respecto a esta tallita de Adobe, encontrarán dos artículos a los que hago referencia. Uno en inglés, bastante extenso y otro en español más [...]
July 10th, 2008 at 19:17
Wow! This is incredible. I was workin on a CSS when the same thing happened to me. I reinstalled Dreamweaver and the problem persisted. Then I read your article. Sure enough, I checked the size of the file and it was 8 192 bytes. Thank you for the solution!
July 11th, 2008 at 9:42
Incredible.
I just had exactly the same problem.
Thankyou so much for this invaluable information.
The curious thing is, the CSS file I was editing was created by Dreamweaver 9 itself one of the Spry applications.
How about that for a paradox / oxymoron.
July 14th, 2008 at 6:03
I also had this problem. This is pretty funny and sad for the engineer who wrote that portion of the code.
July 15th, 2008 at 10:31
I can’t believe it either, thank you, thank you and another than you for this fix, I was just about to reinstall and everything!!!!!
Saved so much time
July 17th, 2008 at 17:44
Wow! This is an unbelievable error…
too bad i reinstalled dreamweaver and it took an hour…
thanks!
July 18th, 2008 at 8:49
Wow, this just happened to me and I was dreading what I needed to do to make Dreamweaver work again when I found your post. Thanks for the miraculous fix. I would have never figured that out on my own. You saved me tons of work I would have had to go through to try to fix this problem.
July 26th, 2008 at 0:05
OMG… this just happened to me too! I thought at first it was a problem with DW, but re-installing it didn’t work. After another half hour or so of trouble shooting I came across this post, and WOOT, it’s fixed.
Thanks a million!
July 28th, 2008 at 8:20
Same problem, same file. Thanks for your time saving post.
July 30th, 2008 at 17:47
Man, this post saved me a LOT of time!
Thank you
August 5th, 2008 at 11:41
Unbelievable but true!!!!
Thanks for the tip.
August 8th, 2008 at 17:58
Well Wow,
I could just tear out my hair as to the aggravation this issue caused me, uh.
I am very thankful to find this article, and to those that found it first.
I really hope that Adobe will find a fix to the issue and give us all a patch to it, but at least if it comes up again I know what to do.
August 15th, 2008 at 7:17
Thank You Mike – bug exactly as you explained – you saved my ass – your fix was simple and it worked a charm for me – fantastic job you done.
August 22nd, 2008 at 9:26
Oh my God! I can’t believe it, but it worked. I spent two hours reinstalling the software and nothing happened until I decided to google it and found this site. Thank you, it’s a great help.
August 30th, 2008 at 21:10
What a joke Adobe.
Thanks for the post!
September 1st, 2008 at 19:03
Wow! Thanks. You’re article just save me a few hours of work. Thanks for keeping the article available.
September 2nd, 2008 at 10:36
Incredibly, I was bitten by this nasty bug, but my first Google seach found this page. Truly weird, but thanks, Mike, for this bizarre and miraculous finding. It saved my day!
September 3rd, 2008 at 12:15
I too have just found this bug today and couldn’t work out what was going on.
Thanks to this post I’ve managed to get back to work again.
September 4th, 2008 at 14:04
Just happened to me – wondered what the hell was going on but remembered reading something like this before and found this site. Sure enough the above is true and I was up and running again in no time – nice one
September 5th, 2008 at 6:26
We can add files that equal exactly 16,383 bytes to that “Not a byte more, not a byte less” bug list.
Thanks so much for the clues that led me to fix my Dreamweaver issues; awesome!! :-D
Tim
September 5th, 2008 at 23:38
You saved me a lot of heartache. I Googled my issue and within 10 minutes I had your fix. I have always been a David Powers fan and that accolade has not diminished. Interestingly, my css file was a multiple of your base figure!
September 7th, 2008 at 3:37
Apparently this also works for multiples of 8,192 bytes. I was editing the size of some padding when my file hit 16,384 bytes and it crashed.
September 8th, 2008 at 20:07
Well done Mike for posting this! Had the exact problem you had… I was actually busy editing a CSS file when I had the crash. CSS file was 40,960 bytes. Fortunately I did not have to re-install or delete anything.
September 11th, 2008 at 2:09
omigod. unbelievable is the word. i spent hours uninstalling, reinstalling, googling and pulling hair. thanks a million! (actually, thanks 8,193 times!)
September 15th, 2008 at 13:37
My problem is I have heaps and heaps of files that are that file size including html. Why is this? It is a new program and I havent created anything Not just a .css style sheet. Am i supposed to delete them all? Most say file size (for example) size 7.64kb but size on disk 8,129kb. any help with this is greatly appreciated
Kyle
Australia
September 15th, 2008 at 13:51
Curious that you should have so many files at exactly that size! Well, if you want to continue to use Dreamweaver CS3, I suggest that you do a batch Find and Replace and just add some whitespace to them outside of the Dreamweaver environment. There are lots of tools out there that can help you to do that.
September 16th, 2008 at 2:23
I hate bugs! Thanks for the “raid”. I was smart enough to search for this before reinstall and install the evil loop of trying to fix something. The file size is a mmmmmm, very suspicious, and a CSS to boot in CS3.
September 16th, 2008 at 14:47
yes very frustrating. Will look for one. thanks mike!
September 19th, 2008 at 3:05
Wow, this is a super odd error in Dreamweaver. This would have been the last thing I would even think about, if at all. Thanks a lot for this post, it worked wonders! :)
September 21st, 2008 at 5:10
OMFG… thanks for the gint. Dreamweaver is running fine know.
btw, I’m from Chile xD
September 22nd, 2008 at 9:39
You have to change your header “Not a byte more, not a byte less” because css file size of a 40 956 bytes (40 960 would be a multible of 8192) would also make dreamweaver to crash. I used notepad and added some whitespace and everything is fine again.
If you have this kind of crash problem first try to rename your site folder name. If dreamweaver will start properly you know you have this file size problem. Add some whitespace to every file (css, htm, php,…) and try opening dreamweaver. It should do the trick.
September 23rd, 2008 at 21:48
Thanks for posting this, Mike. My css file size was 39.9k. Edited in gasp Frontpage and saved it and that did the trick. You saved me a lot of hassle having to find the cs3 suite and re-installation.
September 24th, 2008 at 23:32
Hi, just had this problem, Thanks for posting this. I have the feeling you just saved me a good few hours. Nice one!
September 26th, 2008 at 4:09
THANKS Mike! I never would have thought of this. I couldn’t even remove Dreamweaver to re-install it, it was a pretty hopeless situation. Your explanation and fix worked to perfection, and I too was on a tight deadline. I have to admit though, I actually got a good laugh when I checked my CSS file size and it was exactly 8,129kb. Thanks again!
September 26th, 2008 at 9:31
This is amazing.
It sounds like Adobe is aware of the problem??????
It seems like this has been around for awhile at this point, since CS4 is due out in about a month.
They have no fix on this as of 09-25-08??
Thanks for pointing this out, can’t wait to tell people about this in my class that I am taking right now. Someone else was complaining about not being able to start up DW.
You have saved me a ton of time, though it still cost me 3 hours or so.
September 27th, 2008 at 17:16
Excellent Fix, Thanks! I am currently using Dreamweaver CS3 on Microsoft Vista Ultimate. I was editing a css file when dw suddenly crashed. I tried starting dw again and it crashed multiple times.
My Fix: I opened my .css file into notepad, you can click anywhere after the } and tab your spacebar 3-4 times and save the css file. Re-open dw and behold, it works.
September 29th, 2008 at 23:35
Sure enough, your fix worked for CS3 on Vista 64-bit. My CSS file was exactly 8192kb. I added whitespace like you suggested and restarted DW. Started fine. THANK YOU!
Another problem I occasionally have is that “something” gets corrupted in a DW config file while I’m trying to upload, usually a CSS file, and DW crashes. The fix I’ve used for that is to go into the DW system config folder and delete the WinFileCache-(random number).dat file. On Vista this is in the Roaming folder. I created a desktop shortcut to the folder because I find that I do have to delete that file on a regular basis. (or type %AppData%)
October 1st, 2008 at 16:51
Worked. Unreal.
Important to note it seems to be related only to .css files. I found various other “8,192 size on disk” files in my site. But when I changed the most recent 8,192 .css file I had been editing–poof. Magic. Crazy day.
Thanks for the fix. I was almost ready to run the whole uninstall script (CS3Clean.exe). Not a good choice; as this would have removed the entire CS3 suite and deleted various registry entries. Whew.
October 1st, 2008 at 18:20
That is it! I was getting ready to reinstal/update my CS3 package, but then decided to do a quick search on DW CS3 not starting up and this was the first thing I found. I was updating a CSS file last night when it just shut down.
Great article, Thanks So Much.
October 1st, 2008 at 22:59
This is probably not at all related, but maybe? A few days ago I was working in Dreamweaver and photoshop going back and forth.Sizing images, saving, putting to a page in Dreamweaver. Suddenly the CSS was all gone! Don’t know how it happened, but it had vanished. I move pretty quick from photoshop to Dreamweaver and figured somehow I must have deleted something I shouldn’t have. I got the CSS file back from the server, all better. But today I was working in Dreamweaver CS3, same as before and when I switched to add a photo to a different page the CSS for that page wasn’t there! But the file was still in Dreamweaver this time. Only the page I had been working on prior had CSS applied to it. I freaked and closed Dreamweaver and Photoshop. I opened Dreamweaver back up and it was ok again. Any thoughts? My site is now over 100 pages. I have a TON of images, not in any folders, just listed. (didn’t know much about folders 6 months ago when I started) I read somewhere a long time ago that Dreamweaver “stops working” when the site gets to be over 100pages. I laughed. NOT laughing now! any thoughts. Adobe’s never any help.
Thanks!
The site is http://www.isuckatgolf.net
October 2nd, 2008 at 10:54
Hi Ken,
Dreamweaver used to be terribly buggy and notoriously unreliable. Back in the days of UltraDev, it used to crash regularly and exhibit other unusual behaviours. It has improved a lot in recent years, but you still find that “real” programmers despise it.
I’ve stuck with Dreamweaver through force of habit, I suppose, though I’ve had periods of using Visual Studio, PrimalScript and of course Notepad.
Assuming you’re using Windows, what you saw with the screen appearing blank is probably one of a host of quirks that seem as much to do with the operating system as the software. I find that even Notepad appears to screw up sometimes with big files.
It might have to do with a lack of RAM (for it most often happens to me when using rubbish workstations), or maybe something else, but it’s usually fixed by a quick Minimize and Restore of the offending window. If that doesn’t sort it, I still wouldn’t worry too much – with a display bug, the file itself is not being affected and that’s what matters, after all.
Unless, however, you can isolate the circumstances and repeat the bug with some sort of regularity, you’ll just have to think of it as another irritation of a life lived surrounded by machines!
October 2nd, 2008 at 21:51
Ok i didn’t read all the comments here.. but holy crap that worked. I freaked out (as most of you did cause you’re in DW 24/7) … and i’m thinkin there is no way this is this gonna work.
Found the file, 24,576kb. Edited. Opened DW.
you’re a life saver, thanks.
October 2nd, 2008 at 21:51
OH — and yeah, mine WAS css also, if that helps.
October 2nd, 2008 at 22:35
Oh my God ! It worked … it worked !! You just saved me 2-3 hours of work. I might have just gone ahead and reinstalled Dreamweaver. I thought I did something wrong and that messed up Dw. I was looking into my code to see where I went wrong. Thank you so much Mike !! This article was so helpful.
October 3rd, 2008 at 23:24
I had this problem with CS2 on Windows i got so fed up with it that i solved the problem by moving to Mac and purchasing CS3. Everything was running smoothly until Dreamweaver decided not to launch any more. I found this page and thought my prayers were answered, I changed the folder name but the application still wouldn’t launch fully. When I checked for files of that size I didn’t have any..
I managed to get around the problem by ‘drag & dropping’ the file in to (currently not open) Dreamweaver on the dock, causing the application to launch. I obviously hadn’t tried this before and it is an easy solution because it causes Dreamweaver to load in a different way.. Poor show from Adobe!
October 4th, 2008 at 16:04
Just to remind readers that, though I think I made this clear enough already, this is a Windows-only bug. Thanks.
October 6th, 2008 at 17:24
Unreal – this was my problem exactly. I added some whitespace to my all.css file and that fixed it – thanks for publishing this!
Kurt
October 7th, 2008 at 3:41
Thanks Mike,
Just read your response. I think it was just one of those things too like you said. It takes the steam out of you a bit however when you see how quickly it can “all be gone” if you do something really stupid! Hey, here’s a long shot. Do you know of any way to not have to put the whole site when you add a new page to the spry menu tab? I just waited an hour for my site to put because that’s the only way I know how to do it when I add anything new to the menu tab. I tried just putting the spry tab, maintemplate and the new page itself but it didn’t work. thanks!
ken
October 7th, 2008 at 9:31
Hello again, Ken.
Short answer is that I have absolutely no idea, sir. I don’t use any of the Spry controls in Dreamweaver. Sorry about that.
October 8th, 2008 at 17:43
You have a great site, I have the dreamweaver crash. I tried your solutions (didn´t work but never mind), I have a massive CS3 crash, so far I´m getting no response from Adobe (except for asking me questions about stuff I already told them), I notice someone had a licensing problem and wondered how she resolved it?
October 8th, 2008 at 22:53
Hi Elaine,
Thanks for your comments. I wouldn’t hang around waiting for Adobe if I were you – they’re about as much use as a chocolate fireguard.
Perhaps you could post your issue. I’m no expert of course, but I’ve been using DW since the dawn of time, so you never know. What’s important is what you were doing when the crash happened, what operating system you’re working on, what if any error messages there are, and what’s happening with it now.
October 9th, 2008 at 5:12
wow, like seriously? I could not believe it so I went into FTP and sure enough, 8,192…. wow how unbelievably ridiculous could that possibly be?
October 10th, 2008 at 17:50
Hi Mike,
Thanks for that, I´m going slightly mental trying to sort this one. I´ve been using CS3 for around 12 months, with only a few minor problems.
First problem is I´m running English software on a spanish “speaking” Windows Vista laptop. So although I can follow most paths sometimes its still a struggle to find the right named file when its something different.
Its some week ago now that this problem started, I was working in dreamweaver for several hours sucessfully, on trying to upload my nicely altered files to the server, I got the “crash”. Trouble is the whole of my CS3 suite is affected, photoshop, fireworks etc. (Web CS3 edition), only Acrobat works, Dreamweaver just won´t launch at, Photoshop teases me with a flash of a blank page before disappearing.
I thought it could be the license, so I downloaded a patch from Adobe, but it won´t install, (something to do with access permissions I think). So I tried to follow the manual instructions, but can´t find the specified file, so if anyone knows what %ALLUSERSPROFILE% is in Spanish that would be really useful! Still don´t know if that´s the problem though. I´ve trawled spanish posts, to see if I can find the same problem in Spanish but no luck.
I´ve uninstalled it and re-installed it 3 times to no avail.
Any ideas at all would be most welcome.
October 11th, 2008 at 1:01
Thank the universe for Mike Padgett! I was going absolutely bonkers on this one. I had three CSS files that were causing the problem: one was 8192 bytes, and the others were multiples!
ACK!
October 16th, 2008 at 2:59
When are they going to patch this ridiculous bug?
October 16th, 2008 at 4:41
Another happy customer! Thank you! And I am using DWCS3 9.0.3481, which I believe to be the latest version. Sigh.
October 20th, 2008 at 10:06
You sir, are a genius. I added a fluff comment to my CSS file and everything is working again.
October 20th, 2008 at 11:27
Unbelieveable. Similarly had a crash at 10pm on a Friday (it’s always at the best time!).
I have just found this thread, and was surprised to find the CSS file I was working wih was 8,195 bytes. I thought I would try this fix anyway, and despite the disbelief of my colleagues, it worked a treat.
Really saved hours of head scratching – thanks.
October 22nd, 2008 at 21:50
Incredible help. I was racking my brain trying to figure out why Dreamweaver CS3 on our computer kept crashing on startup. Low and behold I googled, came across this article, checked our style.css file in the project, and it was 8,192 bytes exactly. What are the odds!
Needless to say I edited the file outside of dreamweaver and it is now functional again.
I thank you. Our clients thank you.
Many thanks and God bless you.
October 23rd, 2008 at 23:48
Good lord I’m glad i found this via Google. After trying everything short of a re-install I was about to call Adobe on this, as it would happen at the exact time I was working on a rush project.
Here’s hoping Dreamweaver CS4 behaves better.
October 24th, 2008 at 15:28
thank you very much for such a simple solution. i couldn’t believe ti was that simple. lol I’m at work right now and had to do a lot of editing to a client web site when DW crashed and would not start. You just saved me hours of frustrated attempts to fix it and loose valuable time. YAY
October 26th, 2008 at 1:10
Yep!! This happen to me too yesterday. I could not figure what the heck happened. Who would ever think that a file size would cause this. I searched google for an answer, but no go until I read this post. Indeed we appreciate you sharing your solution with us. It worked for me, but the file was not a .css page it was a .tpl page!
MsKitti
October 27th, 2008 at 15:19
Hmm, so i’m having similar troubles right now, some files just add a couple of irrelevant comment lines or some such and they stop doing it, but I have a couple of persistant files which keep doing it, even though file size isn’t one of the magic numbers.
October 28th, 2008 at 17:07
Thanks for the post, It took me a while to remember what files I was working on yesterday when DW crashed. I didn’t need to run it again after it crashed so I didn’t try to re-start it until this morning when I got the crazy start screen flash then crash.
When I started looking for 8,192 files I had bunch throughout different sites, but then I remembered that I was working on a couple of CSS files both of which were 8,192 so I added some comment lines to the end of the files and I was back up and running.
I sooooo glad your post showed up as number 3 in google when I searched for ‘dreamweaver cs3 crashes on startup’.
FYI: this bug doesn’t appear to affect DW8 since I run it on another machine in the office and I could open and run DW with the same site defined.
November 3rd, 2008 at 0:17
Thank you sooooo very much.. I was ready to publish the site and then this happened…It was like a black hole….
This trick worked…I am so thankful for taking time to explain it…
November 3rd, 2008 at 19:09
Worked perfectly for me by using notepad to edit the CSS file. Thank goodness for me that you published this site! Thank you!!
November 4th, 2008 at 21:21
I’m imagining Adobe execs:
“Jolly good show! Look at what our customers will put up with! Look at how much they depend on us! They wouldn’t change products if we built CS5 out of sawdust and tinfoil and charged $5k/license! *throws full bottles of champagne out window of high-rise corner office*”
November 4th, 2008 at 22:25
Just happened to me too. In my case the file was 16,383 bytes according to Windows. Adding some carriage returns to the end of the file fixed it. I’m also on v9.0 Build 3481.
November 5th, 2008 at 11:59
Unbelievable! Just happened to me – did a repair and still nothing. Did a google search for “dreamweaver cs3 wont load” and lo and behold here you were. Thank you very much – up and running again.
November 6th, 2008 at 10:55
Wow I dont belive this. The exact same thing just happened to me, I found this page through google and wouldnt you know; 8,192 bytes. You just saved my day :)
Cheers!
November 7th, 2008 at 3:44
This is the most bizarre, unnecessary error. Of note is that I was unable to simply restore the folder name and relaunch. I had to completely delete the site profile within dreamweaver and re-create the site in site manager.
November 7th, 2008 at 3:47
Neglected to Thank You! Without your fix I would have wasted a significant amount of time troubleshooting, Thanks so much!
November 11th, 2008 at 0:23
You just saved my day big time – Thank you. As you, editing a CSS file, click save – crash. What-the… Reboot, no go. Googled, found this article and yes the CSS file was exactly 8,192 bytes. As per your instructions, added some white space in Notepad and Dreamweaver starts again. Thanks again.
November 12th, 2008 at 2:46
Why do we continue to support Dreamweaver? This bug is uncall for and so careless of them. This bug has caused so many frustrating hours waisted. I still have yet found which file crashed it.
I simply will just uninstall it and find another software to use.
November 12th, 2008 at 10:24
#102, Andy:
I totally understand your frustration and I remember having similar feelings – particularly because it happened a couple of times before I figured it out. I would also agree with your implication that there are lots of good IDEs out there and in the interests of supporting development out there, everyone should try a few.
It’s force of habit that keeps a lot of folks coming back to Dreamweaver, as does its integration with the Adobe Creative Suite (I don’t personally use the majority of titles in the suite, the major exception being Fireworks).
And despite its occasional bugginess, which has decreased significantly through the cycle of releases, I like to use Dreamweaver simply because it’s better the devil you know “after all these years”. My moans about Adobe are therefore generally confined to matters of licensing.
For example, getting Creative Suite to work in Linux / WINE is painfully difficult even though you have a perfectly legal licence to use it. If you do succeed (using the Win98 setting), performance is often horribly impaired.
Aside from that however, I have to admit with some reservations that most of my grumbles tend to originate from the same source as my positive feelings about Dreamweaver. For me it comes down to the fact that I believe that, for experienced developers anyway, Dreamweaver has not significantly changed in years.
How this works both ways is that, on the one hand, I don’t appreciate the successive bundles of bugfixes and cosmetic upgrades being packaged and sold as “new versions”. On the other hand, however, it can be seen as a huge positive, since the product shows itself to be basically sound: if it ain’t broke and all that.
Thanks for your comment and I really hope you managed to find the source of your problem. And if you did uninstall Dreamweaver, I’d like very much to hear about your experiments with other software, since I’m trying out a lot of new tools myself at the moment.
November 13th, 2008 at 13:54
GREAT!!!!
It solves my big problem
November 14th, 2008 at 14:23
Big Thanks for this article – I’ve been using Dreamweaver for years and this is the second time I’ve encountered this 8,192 bytes bug. The last time was so long ago, I’d obviously (with it being such a bizzare bug) forgotten how to fix it, so thanks again for this useful advice.
November 17th, 2008 at 16:54
This is really unbelievable. I just had a similar issue, and removing a folder and adding files back in one by one finally found me the offending file. It WAS a css-file, but its file size was 2.22kB, which is nowhere near the 8k sizes. In my case, it seems as though some invalid css broke DW because I pressed CTRL+S in the middle of a declaration. So if you have a similar issue, check your css for validity!
And thanks a million for your post. I was about to reinstall but decided to search first. Boy, am I glad I did!
November 19th, 2008 at 15:38
Thanks Mike!
Just ran into this bizarre issue and your info saved me possibly hours of valuable time!
November 20th, 2008 at 12:54
Thanks ever so much – worked a treat – how did you find it out :)
November 22nd, 2008 at 21:01
Wow! Great fix! I found this on Pg1(#8) on Google.
Saved me from having to redo the page I was working on!
Thanks a Ton!
November 23rd, 2008 at 22:32
When I stumbled across this page, I laughed. I doubted this was my problem and that such a simple fix would keep me from hurling my monitor into a wall.
But it worked. Just like that. I right clicked my css file and there was the devil’s number, 8,192 bytes.
Out of curiosity, how long did it take you to figure this out?
November 24th, 2008 at 9:07
Hi Mary (#110), Eric (#108),
I was a very early adopter of Dreamweaver CS3 and this bug hit me quite soon after I started using it and on more than one occasion.
First, I tried other solutions that had worked in the past (reinstalling Dreamweaver, clearing out config files). So because in the interim both colleagues and I had worked on the problem files in other editors thereby changing their sizes, the measures taken “appeared” to have done the trick.
Anyway, there was nothing to be found on the Internet, since it was so soon after the version of DW had been released. The time I found out about the 8,192 thing, David Powers had only just posted his comment as described above. My action was therefore simply to help publicise the fix because by acting as a multiplier, so that others might find it more quickly than I did. Nowadays, there are of course many more folks who have multiplied the fix, though very, very few of them credit David Powers.
So if you want to know what sort of forensic hunch brought David to the fix, you’d have to ask him and I’d be interested to know too. Given his distinguished background, though, it’s probably no surprise he sussed it out!
November 25th, 2008 at 0:38
Hi Mike…
I don’t know if you’ll get this or not, but I had this exact same mistake happen to a PHP file of mine in DW-CS3. I spent a couple of hours researching online to see why my DW program had suddenly crashed and nothing applied until I came to your article.
I thought “No way! What would the odds be?” But when I looked at the Properties window of the last file I knew I had been working on and it read 8,192 bytes, I COULD NOT BELIEVE IT!
But it was.
It took me less than a minute to fix it according to your blog and now, I am happy to say, I am back in business!
Thankyouthankyouthankyou!
It’s like such a small thing, but if you don’t know how to fix it or where to look, AND if you hadn’t have posted this blog, I don’t know what I would have done.
Again, thank you!
Teri
T&I Grafix
November 25th, 2008 at 9:29
Glad to hear you’re back up and running, Teri!
November 25th, 2008 at 16:43
Genius. Saved us a load of time and money. Thanks!!!
November 25th, 2008 at 21:09
Hi again…
I just had to include this. I was just reading some former comments above and actually, when I fixed the problem yesterday with the one PHP file, I thought it had fixed everything. But when I tried to load the folder again, it crashed DW again.
I looked through all the files in that folder and I checked all the files that said the file size was 8kb and I found something that Kyle above (in post #53) mentioned. If I had a file that said it was 8kb, I opened the properties window and it would say File Size: 8.42kb (or whatever) but the File Size on Disk was exactly 8,192 bytes. I had 4 files total that this happened with only in that one folder.
So I did just change all 4 files like you said and I haven’t had any more problems, but I thought that was interesting that Kyle above also mentioned that File Size on Disk thing. Not sure why both of those numbers wouldn’t be identical, but anyway… there you are.
I’m just so glad to be working again without any more problems or crashing, etc. It really is an amazing fix!
Happy Thanksgiving!
Teri
November 26th, 2008 at 14:13
Hi, Teri!
There’s a difference between the file size and the size on disk because the former is the actual size of the file and the latter is the amount of space allocated to it on the disk. These folks have it down:
http://forums.aliensoup.com/showthread.php?t=6985
Accordingly, the relationship between the figures always depends on the nature and composition of the file.
Elsewhere, unfortunately being based in Europe I don’t get to enjoy Thanksgiving, so I’ll have to wait until Christmas for the holidays. Nevertheless, the festive markets are now starting to open here in Brussels and in the secret freezer containers, the magical ice sculptures are already taking shape.
Happy Thanksgiving to you and everyone over there in the States!
November 28th, 2008 at 3:41
Wow. You saved me hours of frustrating trouble shooting. Late last night DW CS3 crashed and I rebooted my machine. Tonight I fired up DW and nothing, your article was the first one I checked on google. Thank you.
November 30th, 2008 at 3:01
Thanks a million Mike! Would never have figured this one out without your help. It’s an obscure bug but seems to me it’s been around for some time (mininum 11 months) and would seem worth patching by Adobe.
November 30th, 2008 at 23:43
[...] by Mike Padgett. Check his great article about this [...]
December 12th, 2008 at 17:07
Crazy, my CSS file wasn’t at the dreaded 8,182 bytes but hovering at 14kb…opened it up in notepad as Dreamweaver would only flash and close.
Added a few lines of comments to change the file size and now all is well.
Thanks!
December 15th, 2008 at 19:10
Wow, second result on google for dw cs3 crashing and i get this site with the same problem. 8,192!! crazy!
December 17th, 2008 at 8:29
Hi Guys,
I found a reason why my dreamweaver was being crashed on startup, it also might be same problem you are facing,
just wanna to share my experience,
just check if any one of your CSS file contains following at the top of your CSS file,
‘@charset “utf-8″;’
just remove it from any other editor(notepad, any text editor), and dreaweaver will load fine,
if problem still persist, you can try to rename ‘Configuration’ folder located in following location
C:\Documents and Settings\{username}\Application Data\Adobe\Dreamweaver 9\Configuration
on startup dreamweaver will recreate it and that may also solve ‘dreamweaver crash at startup’ problem
take a try,
bye
Vinay Rajput
December 23rd, 2008 at 16:28
I know this serves little purpose in helping out others, but I have to congratulate the genius who found this bug and saved me hours in trying to fix it.
Saved my bacon, thanks!
December 23rd, 2008 at 23:17
It was corrupted CSS styles data for me not file size; a few lines of code got messed up which once cleared out worked fine.
January 4th, 2009 at 18:54
Thank you! I was crying here and couldnt understand what was wrong! But this worked! And no i didnt believe you! :)
January 6th, 2009 at 18:24
Many thanks
January 9th, 2009 at 20:08
I was editing my html file, dw crashed, i rebooted my computer. Then DW didn’t start. I checked the size of my html file, it was compressed, showing 22Kb total which was 8.192bytes on disk!
I renamed, tried to increase the size, deleted the file.. Nothing happened. DW still crashes on splash screen while “initializing server behaviors”.
I really need help on this :/
Thanks a lot.
January 9th, 2009 at 22:54
As with every previous comment…wow…thanks so much! 32768 (x4 multiple) jumped out at me as soon as I read this…amazing, this would have been days of investigating…
January 9th, 2009 at 23:01
Hi Yamac,
It does sound like the same bug, but it’s strange that you’re still getting the problem even after you changed / deleted the 8,192kb file.
Have you got any other 8,192kb files in the structure of your Site? Other folks have also reported the fix working for different sizes (usually multiples or divisibles of 8,192kb).
You could also try Vinay’s (#122) suggestion above if that doesn’t help. That’s a different bug but it has similarities.
Please let us know if you succeed and I sincerely hope you do!
January 13th, 2009 at 14:17
Unbelivable!!!
That was it!
January 14th, 2009 at 3:53
I can’t believe it worked!! thanks bud
January 14th, 2009 at 19:26
Thank goodness for this information. I spent an hour on the phone with IT support, trashed the cache, and a variety of other things to get the app to open. Unfortunately any time that I opened a file attached to or the CSS file with the 8192k file size, it crashed. I added a line of comment code and I’m good to go. Is this some programmer’s idea of a rotten easter egg?
January 15th, 2009 at 21:42
Thanks for tha help, solved my problem. how odd, reminds me of the adobe DW daylight savings bug.
January 15th, 2009 at 21:50
Thanks mate! unbelieveble. You helped me so much!
January 17th, 2009 at 20:58
WTF????? This is the most ludicrous bug I have EVER heard of. It’s like your car cutting out if you do EXACTLY 34.6mph for 10 seconds. I can’t believe that this has wiped me out for a day……:( Thanks SO much for the fix.
January 19th, 2009 at 16:15
OMG!!! This is weird! This happened to me, and all of the developers I work with were in shock. C’mon Adobe fix your issue. It’s funny because a lot of the customers for dw could figure out how to patch the bug. Anyhow thanks for your post, I will relay your findings to other poor souls. Does anyone know of a Patch release?
January 19th, 2009 at 17:05
[...] http://www.mikepadgett.com/technology/technical/dreamweaver-cs3-crashes-and-wont-start-up-again/ [...]
January 20th, 2009 at 16:21
You are the man! My dreamweaver crashed last night and I just gave up and went to bed. I try to open dreamweaver today and find that “initializing files” is where it hangs up and sends an error. I went to a few different sites to find the answer and who would have thunk that its as easy as changing the name of a folder name.
Thanks so much!
January 20th, 2009 at 18:43
[...] right now I am completely baffled! I came across these two articles: Number one at Mike Padgett.com and the second a link from that site to David Powers on Google [...]
January 20th, 2009 at 18:59
Oh, my!
That is re-donkulus!
!!
January 21st, 2009 at 21:43
This just happened to me twice in two months. 8,192 bytes. Crazy.
January 22nd, 2009 at 14:09
cheers Mike, you have saved me a lot of time here.
inexplicable!
January 27th, 2009 at 13:33
Hi Mike,
You are a life saver!
Quick search on google with this exact problem and there you were. Phew.
Like many others, I open a blank file and start coding for a good long while especially in CSS files and library files and get this error all the time.
What I have also noticed (now that all is explained) is that I sometimes go just over the 8,192 bytes and it crashes but I am allowed to restart dreamweaver as it may have got to 8,194 bytes as it crashed.
Anyway when it suddenly hits the exact problem talked about here I am really glad that i’m not just unlucky and have a rubbish computer…
Thanks again.
January 27th, 2009 at 21:38
Hello Mike,
You have saved me a lot of time. I’ve found your comment whithin 5 minutes and it seemed i had the same problem.
good job,
February 5th, 2009 at 16:55
ADOBE DREAMWEAVER MX, ADOBE DREAMWEAVER CS3, ADOBE DREAMWEAVER CS4, ADOBE, ADOBE, ADOBE.
ok the bit above is for seo, hopefully this would add even more ADOBE keywords into this posting.
i have been trying to download image files via ftp, ok there are quite a few (about 5,0000) and every time i do Adobe Dreamweaver CS3 crashes, and says “out of memory”.
however i have 2 GB of ram, and not even 1/2 of it is being used, so from my point of view this is nothing to do with ‘lack of memory’.
so, i ring up adobe uk – who forward me to adobe usa – who after doing some fairly obvious things came up with a solution!
stop using ftp in dreamweaver and use another product.
so i ask to make a complaint, the answer .. no you cant.
so i ask to esculate this to another adviser .. no you cant
now i have just read the above posting its seems amazing that Adobe has not been sued, either personally or by the DTI – as clealry their products ‘are not fit the purpose they were bought for’.
anyone agree?
so know i have to go check over 4,000 images on their sizes! arrhhh
** was the statement correct that it can be *ANY multiple of 8,192 eg 16,384 etc – can someone confirm, or not, this??
excellent posting, thanks for the information.
February 5th, 2009 at 16:56
update to above posting, not 50,000 images but 5,000.
February 7th, 2009 at 7:48
This has got to be one of the strangest bugs I’ve come across! Work around worked great, thanks!
February 11th, 2009 at 8:01
This worked like a charm. I suspect that if people have been getting this as routinely as we have listed, then it’s likely something to do with editing one of the pre-made features of Dreamweaver. I was editing the CSS file for a spry tab widget when it occurred. I read this article, then added some white space to the bottom of the CSS file and voila! I’m back in business. Thanks!
February 17th, 2009 at 16:44
Many thanks for this fix ! It saved me a lot of grey hairs !
February 19th, 2009 at 0:31
Wow, thanks for the tips. That’s the weirdest bug I have ever seen. I only move my css file, and then, DW came back, alive, like a new born.
Well, I kept my file on another folder, so I will change some values to keep it out of the monstuous “8,192 bytes”.
Thanks again
February 19th, 2009 at 16:15
i think i love you! many many thanks. just backed up my computer … twice :)
February 21st, 2009 at 21:44
Oh how I wish I’d found you first! But many many thanks nonetheless. Unfortunately I tried everything under the sun. My only consolation is I may have fixed a number of unrelated but bothersome vista bugs along the way. sigh.
I took the advice of one of your commenters and went on over to the Adobe bug report page, so blithely called a wishform. (Because wishing is all we get?)
http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
This is what I told them:
******BUG******
Concise problem statement: DW crashes when file size reaches 8,192 kbs.
Steps to reproduce bug:
1. Edit file within DW
2. Save file
3. …
Results: If file happens to be 8,192 kbs, then DW crashes and won’t restart.
Expected results: Not this, obviously.
This is a known bug! Why the heck don’t you include information about it in your Troubleshooting Dreamweaver page??? Honestly, a little common sense please. I just wasted 6 hours working my way through your troubleshooting steps when one sentence from you could have put me on the right path. Anyone might think you are so embarrassed by this ridiculous bug that you refuse to admit it exists.
******END OF MY WISH******
I didn’t even bother to wish for a fix. Call me jaded.
Maybe if enough of us give them a little kick we can turn wishes into results…?
February 23rd, 2009 at 21:29
Bless you! Bless you! Bless you! I was saving a css file when Dreamweaver crashed and just like everyone else I rebooted the computer but to no avail. Found this on Google and lo and behold my css file size was 8,192. I moved the site folder where Dreamweaver couldn’t find it and Dreamweaver started just fine. I changed the file size by editing the css file in notebook and saved but when moved the site folder back, Dreamweaver still wouldn’t open. I started looking at the file sizes of other documents in that folder and there were 2 others that were 8,192. One was an html and the other was a txt document. As soon as I edited those to increase their file size Dreamweaver seems to be behaving well for the time being. Thank you so much.
February 23rd, 2009 at 22:39
Damn, your good. I thought by chance, lets google the dreamweaver crash problem, low and be hold, other people had the same problem as me, but why?!?! It was my css file at the exact KB (now thats weird by chance). I amended the file in notepad by adding a few more lines of code, which solved the problem. You are Genious!!!
February 23rd, 2009 at 23:49
Thank you for posting this. Had the same problem and the fix worked right away!
February 24th, 2009 at 18:15
OMG, that is crazy. Thank you so much for this information, just wished it would of come a little sooner while I still had hair and my sanity.
Thank you
Thank you
Thank you
February 25th, 2009 at 18:46
Worked for me.
The size of my file was 16384, changed a fews bits and He-presto Dreamweaver works again.
Crazy crazy world.
Many thanks
February 26th, 2009 at 22:59
[...] thanks to Mike Padgett who provided a detailed fix on his site last year. Amazingly, Dreamweaver CS3 crashes when you edit a file to exactly a multiple of 8,192 [...]
March 2nd, 2009 at 0:29
I cannot believe this! I thought I was going mad. Whoever figured this out is truly a genius. A billion thanks to you.
March 2nd, 2009 at 13:27
Don’t know how many times this has happened to me since I got CS3!!
I’ve done some editing on my latest ‘crash file’ in notepad but whilst the size of the file changes, the size on disk is still 32768 bytes which divides by 8192 by 4!! :(
Noticed some of your comments go back almost a year… wish Adobe would pull their fingers out their backsides and get this sorted!!!
But thanks a lot for your tip! I’ll just keep editing in Notepad till the size on disk goes up!! :)
March 3rd, 2009 at 8:09
I was fortunate to have googled “Dreamweaver CS3 won’t open” and finding this article on one of my first hits. I checked my css file and sure enough…. 8,192 bytes. Quite an interesting bug (and hilarious, too)
Thanks!
March 5th, 2009 at 15:26
something odd happened to DW cs3 this week. Now when I start it up it sits at the splash screen doing nothing for about 45 sec and then the standard task screen appears – anyone else have this or a solution?
March 6th, 2009 at 0:15
Thanks for the helpful fix! It saved me a ton of time, what a bizarre bug!
March 6th, 2009 at 17:14
What an amazing bug! Worth keeping as a feature just because its so amazing. Thanks for the help.
March 7th, 2009 at 12:20
Thanks for this solution but I also found that it may not have to be a multiple of 8192.
I have a file the following size (this was a css file)
63.9 KB (65,529 bytes)
This caused Dreamweaver to close instantly.
I simply put a space on the end of any line in Notepad which made the file size: 63.9 KB (65,530 bytes)
Dreamweaver now opens OK (until the next time!!!!)
March 7th, 2009 at 16:03
Mike,
thank you so much for this post.
I was happily working away in DW w/ css file (as you described)..then CRASH! DW wouldn’t reopen. I restart. same result.
did a g search, your post was first.
THANK YOU SO MUCH FOR SHARING. I was just about to fore go all my snippets and customized stuff for a reinstall..then thought I should check online first.
you rock dude!
March 10th, 2009 at 17:23
Thank you so much for taking time to write this. I was so shocked to find that my CSS file size was exactly 8,192 bytes! I followed your advise and Dreamweaver is working again :)
March 13th, 2009 at 14:01
Thank you so much for publishing this issue / solution, you saved my sanity.
March 23rd, 2009 at 17:06
…what if your file size allocation on the drive is exactly 8,192 bytes?
I had one file of the dreaded size, but the small files on the desktop are all given a 8,192 byte space allocation.
Does this also affect Dreamweaver opening files?
March 23rd, 2009 at 20:21
WE HAD THE SAME PROBLEM. I READ THIS ARTICLE AND LOW & BEHOLD :
8,192
I tried opening DW again, but this time instead of letting it run through the cache I clicked cancel and BAM it didn’t read the files before opening and just opened. REALLY EASY FIX, was happening on two computers at same time (Yep, they were accessing the same site with the same file in it)!!!
March 26th, 2009 at 12:13
Thanks Mike, I’m so glad I stopped to read your article on this bug. My file was actually 16384 bytes (exactly twice as big)!
Freaky bug the odds of which obviously aren’t as small as you would first think. I read something somewhwere else that CS4 has a button to stop the site caching process, don’t know if it will solve this though.
I’ve left a link on twitter to this post as I’m sure others will find it helpful.
March 27th, 2009 at 19:01
Thank you so much for publishing this fix, you have saved me my weekend!
BTW I called Adobe support in the UK at 4:45pm Friday to ask about this, to be honest I expected a wait to get through, but I got a message that support was not available and to call another time, what service eh?
Thanks again
Matt
March 27th, 2009 at 22:24
Saved my day! The weird thing that I enjoyed was using notepad to change the file back to 8192, and watching Dreamweaver crash. HAHA, what a stupid bug.
March 28th, 2009 at 2:10
man you just saved my life, my file size was 57344 bytes!
March 30th, 2009 at 9:55
I was totally dumbfounded when this happened to me – fortunately this is one of the first websites I came across. Lo and behold, 8,192 bytes!
I was so surprised I actually embedded part of this article (with a nod to you of course) within my CSS document within a comment as a record. I just couldn’t believe that it had happened to me.
Relief is an understatement. I thought I was going to have to reinstall or worse – upgrade AGAIN to CS4. Frankly I’m just going to wait for CS5 this time.
THANKS!!
March 30th, 2009 at 22:44
[...] was on the verge of reinstalling the whole OS when another of my teammates found this funny article after some research on the net. Exactly like this article says : we couldn’t believe it. I [...]
April 2nd, 2009 at 16:48
I had the same problem but my css file was 16k, so, it looks like the is a problem with any multiple of 8k. I just added extra dummy code and problem solved.
April 2nd, 2009 at 16:53
If fact I just rechecked my css file and it was 16,384. Exactly double…. weird.
April 7th, 2009 at 20:57
Wow.. that’s pretty incredible. Horrible… but incredible.
My file was 16,384 bytes…. divide that in half and you get 8,192.
alright adobe… what have you done now…
April 8th, 2009 at 18:31
you are amazing! i have no idea how you figured that out but you saved my life!!!
Thanks again
April 10th, 2009 at 12:38
Thank you #122!
You saved my day.
April 11th, 2009 at 21:10
You sir, saved me from a mental breakdown! You cant even begin to imagine how appreciative i am that you saved my workday. Thank you :)
April 12th, 2009 at 21:13
I’m not sure if I believe this…I’ve read it all over the web and I searched through my files and didn’t find an 819 byte sized file…cs3 is still not loading for me…
April 14th, 2009 at 18:42
Can I just tell you that this issue has happened to me TWICE!!!! TWICE!!!!!
April 17th, 2009 at 14:50
Thanks for the post, fix worked like a charm.
I had just wasted about 4 hours uninstalling, searching for disks, and reinstalling dreamweaver.
April 18th, 2009 at 2:09
I found you through Google researching the sudden strange behavior of DWCS3 – thank goodness I found your answer! Folks, when I read this first, I thought – ya right…but I went along with it and sure enough…to my amazement my CSS file was exactly the same size. Renaming the site folder enabled me to open DW back up. Adding a simple comment to my CSS file and then saving it fixed the problem. I could then rename my original site folder back to what it was originally.
What a stupid error! I am sure people would actually uninstall DW and would end up going insane from this bug. Thank you so much for posting this answer, you saved me lots of time and stress!
Cheers from Canada!
April 22nd, 2009 at 14:22
What are the chances?! Thanks for the fix on this issue, for a moment there I had that dreaded feeling of having to reinstall.
April 25th, 2009 at 21:24
I cant belive that…. almost thought i was going to have to reinstall!
April 27th, 2009 at 6:23
yep, it’s still out there, still happening in april 09 on cs3…
April 28th, 2009 at 15:01
Cool, thnx! the problem is not gone yet =)
April 29th, 2009 at 18:30
WOW! 8,192 bytes. Who would have ever thought that would have caused such a problem??? Thanks so much for posting this! This saved me so much effort and fixed the problem right away!
April 30th, 2009 at 15:34
Unbelievable – surely the most obscure bug ever? I’d have never figured that one out, thanks for the post!
May 2nd, 2009 at 14:34
Mike, thanks for this priceless post. Without it I’d have been tearing my hair out wondering why DWCS3 suddenly stopped working.
It’s comforting to know that in 2009, there are still bugs around that can make you feel like it’s 1995. ;)
May 5th, 2009 at 10:41
Thanks for this post. When I read the post and saw the 8,192 thing, I thought, yeah, right! Then I checked my css file. I had exactly the same screenshot! Amazing. Almost like magic.
Many thanks again for posting this. Internet and search engines are amazing.
May 8th, 2009 at 5:36
Incredible!…and what a genius to figure this one out. I located the last css file (of course it was 8,192 bytes!), added white space in notepad and like magic all resolved. Thanks a million ;)
May 9th, 2009 at 4:57
Thanks for posting this…. I was stuck in it for around 1 day, tried everything and then I found your solution…..worked like magic!!
May 11th, 2009 at 17:16
Thank you for finding this glitch.
I just about fell out of my chair when I found your solution. This has got to be the oddest error I have ever seen. Sure enough my CSS file was a multiple of 8,192 (16,384).
May 12th, 2009 at 10:24
Utterly unbelievable! thank you for saving my sanity with this madness (and my wife thanks you as well!)
May 12th, 2009 at 17:17
I have been working in DW for over 5 years for my freelance business. Yesterday, I was working in it at the University where I also work (Northern Arizona University – The W. A. Franke College of Business).
I was moving along, developing a css for a new site when CRASH. And on re-start, attempt at re-launch, NO GO (beyond the DW startup screen)!
My IT guy came to my rescue (Seth, my hero) and searched the web and found you.
Sure enough, the css file I had been working on was 8K – I opened it in Notepad and modified it to increased the size and Voila – DW launched flawlessly!
You are now my new hero, as well.
THANK YOU!
tmsr
May 14th, 2009 at 20:30
Holy Crap I did not think it would work. It just sounds too f’ing simple. It worked. I just looked in my site and found a file that was 8k, opened it in notepad, added a lot of white space. Saved it, which made it 9k. I tried opening DW3 and it opened.
May 14th, 2009 at 21:26
OHMYGOD! It could easily pass as an april fools joke, but it is not! Happend to me! I tried almost everything and, then, I just changed the .css file at notepad++. Since it’s not 8,192bytes anymore, dw cs3 is working fine again!
May 15th, 2009 at 20:42
It is the same for vista worked like a charm. Thank you so much. I fumbled around all day only to fine this and fixe the problem in 5 minutes.
May 15th, 2009 at 23:18
I don’t know how you figured this out, but it’s exactly what happened to me. And, your solution of adding more bytes to my css file worked perfectly. Thank you!!!
May 16th, 2009 at 23:34
Wow. There it was, 8192kb. Thanks for this, I was contemplating having to edit with Notepad…shudder…
May 20th, 2009 at 13:01
Unbelievable….. but it just did the trick! This just saves al lot of time on reinstalling etc. Thanks for the solution.
May 25th, 2009 at 19:00
It would appear that this bug comes into play at other file sizes. Came across your solution and did the test of renaming the website folder and got DW CS3 working again. But I had no files at the 8KB size that I was recently working on. The last file I was editing before the crash was a CSS file at 16KB (16386 bytes).
Edited the file to up the filesize and we’re up and running. Take away the added code and DW’s a goona again.
Thought you’d like to know.
Did a debug but too much data to post here.
May 27th, 2009 at 13:41
Many, many thanks for publishing this information.
I spent today probably 10 hours re-installing CS3 and calling Adobe Customer Service in India (where else it could be today?) at least 6 times. They told me – if I pay them $39, they will re-install CS3 and it will solve the problem!
Of course I refused to pay $39, downloaded Microsoft clean up utility KB290301 and Adobe script CS3Clean,re-installed CS3 myself (Why it should be so difficult re-install the software? I don’t get it…)
And… it didn’t help!!! The Dreamweaver was still crushing on Start Up!
And then I turned to the best Customer Service line today – Mr. Google! And found this article. Thanks again you for publishing it!
IT WORKED!
I couldn’t change the size of CSS file, so downloaded the previous version of website from production and it solved the problem!
We should name this bug – 8192_bug. And thank Mr. Google too.
May 28th, 2009 at 13:24
This bug had me pulling out my hair for hours! It’s only because of Google and Mike Padgett that I have some hair left. Thank you so very much!
May 28th, 2009 at 13:33
Keeping whatever you’ve got left of your hair is important, Frank. Glad you found what you were looking for ;-)
June 3rd, 2009 at 19:48
This is unbelievable. Unfortunately for me, my company has several files that are that exact size. I just need Dreamweaver for my own personal site thought and not the company site. How can I delete the site entirely out of Dreamweaver without opening it (considering it crashes every time I try to open it)?
June 3rd, 2009 at 20:02
what is also interesting is that when I check the properties of the Dreamweaver application itself, it is 4,096 bytes. Exactly half of 8,192. Does that have anything to do with this or just a coincidence???
June 4th, 2009 at 9:51
Yes, the smaller file size is probably related. If you want to delete a site in the way you asked, just temporarily rename the actual folder the site files are stored in. Dreamweaver will start as normal, then you can go to “Manage Sites…” and delete the site there.
June 4th, 2009 at 20:47
wow it is STILL crashing! I’d like to just uninstall it and reinstall, but I purchased the product online. Here we go with Adobe support…
June 5th, 2009 at 8:32
Thank you very much for the brilliant solution. Your advise save a lot of my time to fix the bug. The DW working fine after I edit the css file using notepad.
June 5th, 2009 at 12:08
Thanks a lot! I had exactly this problem. my CSS file was 2×8192 bytes long and my Dreamweaver crashed and refused to start again. I filled the CSS file with some /* comments and solved it.
June 5th, 2009 at 14:43
I just uninstalled CS4 because it just kept crashing no matter what I do. Does anyone know how to reinstall it? I don’t have a disc or anything because I bought it offline. I don’t know how to download it again and Adobe support is worthless.
June 12th, 2009 at 20:48
Ok I knew i had an odd problem….but i NEVER EVER thougt it would be THIS odd. Luckily, the solution is as stupid an simple as the problem itself.
June 15th, 2009 at 21:30
oh my god, you save the day man. i exactly had the SAME problem. i cant beleive…
June 16th, 2009 at 17:05
Wholy crap, I was editing a css file and had this exact thing happen. Sure enough, 8,192 bytes. You’re my hero Mike.
June 18th, 2009 at 16:22
Thanks for this information. I just had the same problem today when I made an edit to a CSS file that bumped it up to almost exactly 3 times 8,192 bytes. Tried your fix and it worked like gangbusters.
June 19th, 2009 at 16:50
Well I can’t thank you enough. Exactly the same problem for me too. I almost didn’t bother to check this as I thought it was a spoof but low and behold my css file which was crashing was 8kb. I can’t believe this bug has not been fixed by an update. Shame on Adobe.
June 19th, 2009 at 20:20
Very weird bug. I had the problem, and your solution fixed it. Thanks so much. I was afraid I would have to reinstall DW.
June 22nd, 2009 at 2:16
Crazy – yeah I totally had that problem. Added white space, increased file size, and problem was fixed. Thanks so much!
~ James
June 23rd, 2009 at 21:35
UNBELIEVABLE!
how do they sell a product with this bug.
thanks for the solution.
July 6th, 2009 at 8:51
Great solution for an odd bug.
I had the daylight saving bug before which was solved by removing the winfilecache file, but the failure to start-up caused me to reinstall Dreamweaver CS3. Your solution saved a lot of irritation.
thanks.
July 15th, 2009 at 8:27
Experienced exactly the same issue. Whitespace added to css file did the job.
I have never seen anything like it and would never have thought to try that. Thanks
July 16th, 2009 at 10:55
I accidently did a “open with dreamweaver” to an excel file . My dreamweaver 8 crashed. Now whenever I try opening it a splash screen appears and then nothing happens. I tried reinstalling, even cleaning the registry but it hasnt helped. My OS is win XP. Thanks in advance
July 17th, 2009 at 21:00
Gush, man you saved me. Thank you so much.
You have a bear from me.
July 29th, 2009 at 1:08
Nuts. My CSS file hits 16,384 bytes and Dreamweaver has a stroke. Thanks for saving my bacon. If Adobe was one dude, he’d definitely be murdered by now.
July 30th, 2009 at 15:41
Hah! This is an old post, but I gotta laugh! It seems so silly, BUT sure enough I changed the byte size of the project I was working on and smooth sailing. Damn!
Thanks for the tip
July 31st, 2009 at 4:28
hilarious! yup, 16384 bytes, and even better that yours was the first solution i looked at.
thanks a bazillion!!!!
July 31st, 2009 at 4:50
hmmm… very strange. apparently both files i had open (an html and a css) were saved at exactly 16384 bytes. the odds of that seem crazy low. maybe the size is a symptom of a different underlying, and otherwise benign bug? or maybe i just hit the bytes jackpot.
July 31st, 2009 at 10:50
Crazy. Adding whitespace to css file helped me too.
August 6th, 2009 at 4:40
THanks for this article. I almost re-install my dreamweaver cs3.,.
August 6th, 2009 at 19:30
Thanks for this, I just ran into the bug today.
August 8th, 2009 at 7:02
Thanks for this, I was pulling my hair out.
Also thanks to the poster who mentioned the fact that it would also crash on multiples of 8192. After I altered the original offending file in notepad, DW whould start, but not allow me to use site caching (caused a crash).
On closer inspection of my files, I also found a file sized at 24,575b. Fixed again, and voila, caching worked.
Brilliant, cheers!
August 12th, 2009 at 4:28
I was ftp’ing a wp.mu install and have had tons of problems with incsub.com the company that conducts these installs. I assumed they somehow sabotaged the install so it would not let you pull the site off the server. A quick search and found that the readme file was exactly this size. Still not convinced they didn’t do it on purpose but you are my hero. Thanks for this and I will share the love with anyone I know that uses DW.
August 12th, 2009 at 13:20
Thanks for the info, DW crashed on me (not for the first time) and luckily I found this article very quickly & was back up and running in a few minutes. Sort it out Adobe!
August 13th, 2009 at 15:42
After 5 hours of (not for the first time) repairing uninstalling then re-installing CS3 and still refusing to open I entered ‘dreamweaver cs3 fails to open’ into google. Your article has saved my XP pc from a 3 storey drop and possibly also saved me from following it in despair.Unbelievable indeed, mine was 16384bytes.I will now know in future if this ever happens again which will surely save me so much time = money and frustration.I owe you a drink.Until then thanks very much indeed for taking the time to post this article.
August 16th, 2009 at 1:49
Been using DW CS3 forever and never had this issue until today. Luckily I did a Google search and found your fix before trying anything else. Worked like a charm. Thanks!
August 16th, 2009 at 23:43
I only spent about an hour trying to troubleshoot this problem before finding this article, but I was ready to give up, pull out the rum, and start the re-install! Thank you, thank you, thank you.
August 27th, 2009 at 2:35
This was a life saver! searched for hours and got really scared in one point!
this was an awsome solution! thx a LOT!
August 27th, 2009 at 19:48
Unbelievable. Typical Adobe. Worked for me even though the file did not appear to be exactly that size. Thank god i found this solution first. Only other thing I tried was a reboot.
September 1st, 2009 at 0:49
Unfreaking real, my build version is same as yours. Just the kind of bug that ruins a day. Didn’t clue in fast enough to the available fix, so wasted hours repairing, uninstalling, re-installing Dreamweaver CS3 to no avail. When I saw your graphic with the CSS file, it hit me! I had changed an attribute for a selector when DW died. Modified the css file outside of DW, then DW launched normally. I get the shakes thinking that I almost got to convincing myself that I’d have to remove/reinstall the whole CS3 suite…..
Scarry!
September 23rd, 2009 at 1:48
Thank You SO much. i found this solution first, right after a single restart. I have a deliverable tonight and you saved my behind!
September 25th, 2009 at 9:01
Thank you so much for this I have it so helpful and you have really really sorted a stressful situation for me.
September 25th, 2009 at 19:34
Well cover me with oil and bake me for 20 minutes.
This sorted the problem a treat. I think this is one for Stephen Hawkins to theorise on.
You must be chuffed to see that if you enter ‘dreamweaver cs3 does not start’ into Google, your answer comes out in first place from (about), 340,000 results. It’s a shame I couldn’t find the answer on the Adobe site.
October 2nd, 2009 at 1:54
Mike, you nailed it! Excellent post. Adobe should send you free software for life.
October 4th, 2009 at 13:24
You are a genius! Thank you for saving my bacon!
October 6th, 2009 at 7:14
Wow. I had this crashing issue and when I found this post on Google, i thought: oh, there’s no way the problem could be this simple and the solution so easy. Yet when I checked my file properties, there it was, staring up at me: 8,192. Amazing!
Thank you SO much for this — I’ve been tearing my hair out! Bless you, good sir. :)
October 13th, 2009 at 0:02
I had this issue and found this post. I thought you were insane but when I opened my properites of my CSS file and saw 8,192 I began laughing.
Thanks!!
October 20th, 2009 at 20:54
Great post. I was just preparing to scream and uninstall/reinstall DW when I came across your post. The bug you encountered was exactly my issue. The only difference for me was that I was able to open the site profile without a problem. The problem only occurred when I opened the particular CSS file. Added some white space and the problem went away.
Thanks again! Your solution saved me most of my afternoon.
October 25th, 2009 at 2:55
I had the same problem to, what a bug. Your post have been helpful thanks a bunch!
October 25th, 2009 at 3:01
[...] you have this problem you might want to try Mike Padgett’s solution. Works like a [...]
October 26th, 2009 at 13:50
This page is now #1 for “Dreamweaver won’t open” and thank goodness for that, probably prevented me from losing years of life due to stress and panic. My magic number was 16384.
October 26th, 2009 at 18:56
This is amazing! It’s also amazingly weird, but I’m so glad I found this site.
I was working on my site in the html, css, and the tabbedpanel.css files and this happened. It happened to be my tabbedpanel.css file that was exactly 8,192. A quick fix and I’m back up, but it was only quick thanks to you.
Lifesaver.
October 29th, 2009 at 14:40
Wow. That is freaking bizarre, but thank you!
October 29th, 2009 at 19:59
[...] right now I am completely baffled! I came across these two articles: Number one at Mike Padgett.com and the second a link from that site to David Powers on Google [...]
November 1st, 2009 at 11:27
Cheers Mike, you are a legend.
As I started reading I was thinking you may as well tell me my PC was facing the wrong way, but sure enough, my CSS file was 8,192 on the nose. Quick fix, no problems, thank you!
November 3rd, 2009 at 16:05
Amazing. Thanks!
November 3rd, 2009 at 16:15
THANK YOU! I was about to have major melt-down here, but luckily I googled the problem, and yours was the first thing that popped up. I check my css file and sure enough 8,192! That is so weird, but thank you for publishing your findings and helping me get back to my Dreamweaver quickly!
November 4th, 2009 at 6:00
WOW I CANNOT BELIVE A CSS FILE CRASHED MY DREAMWEAVER!!! IM SO DISSAPOINTED…
November 13th, 2009 at 16:44
In all the years I’ve worked with this product, I’ve never come across this problem until now. My primary css file was at a multiple of 8192 and causing some related files to be 8192. Thanks to you I was able to find the problem and fix it before going through the nightmarish process of reinstalling, contacting Tech Support, etc. You’re a life saver!
November 13th, 2009 at 18:02
Thanks so much for this fix… I have been pulling my hair out over this one!
November 14th, 2009 at 0:59
Found a file at 4096 for the Size on Disk. Opened it and changed it to adjust the file size. Every time the actual file size passes the multiple of 8192, the Size on Disk immediately adjusts upwards to the next highest multiple. Any thoughts?
November 14th, 2009 at 17:14
That sounds strange, Josh (#265). Are you saying that no matter what you do to the file, it adjusts to a multiple (or fraction) of 8,192?
November 17th, 2009 at 0:41
Yep, strange, huh? Just added a whole bunch of junk again to the file and it’s now sitting at 65,536 (8 x 8192) and Dreamweaver won’t start :) If you hear of any potential solutions I’d really appreciate it! Thanks for all of your input!
November 17th, 2009 at 8:43
Incredible indeed! DW crashed, checked my CSS and there it was: 8,192 bytes!
Adding a few lines in Notepad solved the problem!
November 19th, 2009 at 17:56
Wow what an odd error. Happened to me using the latest version of DW CS4. Wouldn’t start up and found this site and looked at my .css file size and it was 4096 exactly half of the 8192. I renamed my folder and it started up fine so I deleted some comments in my .css to change the size and reverted my folder back to the original name and it started just fine! Thanks a lot for sharing this!!
November 29th, 2009 at 10:53
Wow, this has happened to me twice now. I think I’ll bookmark this page. ;)
Thanks!
December 2nd, 2009 at 12:16
Guys – files are stored on disk in chunks in increments of 1024 bytes which is a multiple of 8192. The actual size of the file may be less than 8192 but the “size on disk” always rounds up to the next multiple of 1024.
So I think its rather an issue with a css file and not its size on disk.
I merged 3 css files resulting in one over 12kb and still would not open.
remove that file and it opens fine… so must be a corrupt css or syntax it doesnt like – hmmmm glad to be proven wrong if you can sugest what to try next – maybe a css fixer tool?
December 2nd, 2009 at 12:20
sorry just realised you mean when the actual size is a multiple not just the “size on disk”
December 2nd, 2009 at 12:32
well after much tidying up my css was causing the issue on dreamweaver 9 and it was not a multiple of 1024 or 8192. I’m convinced it was due to corrupt spacing or bad syntax so removed loads of comments and extra lines and opens fine now. I think many here are seeing the “size on disk” multiple and assuming this equates to the “actual size” multiple when really they then go tidy up or merge css which may be removing the actual corruption itself….
again – only my opinion as the thought of a bug by file size is ludicrous :)
good luck
December 2nd, 2009 at 13:16
Hi, Jonathan,
Thanks for your comments.
I’m afraid it is in fact a bug dependent entirely on file size. It’s not too common simply because the probability of triggering it – a file being at precisely one of those multiples – is not so high.
In your case you’ve tidied up your file and in doing so you’ve changed the size of it, hence no more problems. It doesn’t happen because of your syntax, which I’m quite sure is pristine ;-)
December 2nd, 2009 at 16:45
Interesting fix – since my files were already on the remote server, I just deleted all from the local machine and DW opened. Thanks for the help!
December 5th, 2009 at 0:05
thanks, renaming the folder got me out of trouble. I’m not sure if I had a file of exactly that size of 8192 i think it was 24kb so maybe a multiple of that again.
Thanks anyway!
December 7th, 2009 at 0:29
Thanks for posting this! I just wasted 4 hours of my life trying to figure out why dreamweaver was crashing and it was for this reason.
December 7th, 2009 at 10:07
Thanks man! You are a life saver!
December 13th, 2009 at 17:33
That is a crazy bug. Thanks for the fix!
December 15th, 2009 at 11:26
Wowzers! had this issue last night, I tried the RegEdit and Config Folder approaches, neither worked, then your “ridiculous” post did! I call it ridiculous, as I thought it was an April fool joke or something..
Youre a brilliant individual, well done for working this out, and mine too was a CSS file = 8192b this MUST be a DW developer party trick.. lol funny now I’ve sorted the problem..
P
December 15th, 2009 at 11:45
Once again to Paul and to everyone else who’s expressed gratitude here, I can’t take credit for figuring out the cause of the bug. That should go to David Powers. I just wanted to help others to find the solution by writing this article at a time when there were no other references to the problem on the Internet.
Thanks!
Mike
December 15th, 2009 at 15:17
That is SO off the head!!
Thanks so much for that post and thanks to dave Powers for the solution! What a weird thing – I really thought there was a fault on the system!!
Back to work!!
Mike
December 16th, 2009 at 3:29
What are the odds? Try 2 files at the exact same time. oh yes! css and php file both of which I was using to work my layouts and both of them, 8192 bites.
December 16th, 2009 at 23:10
18months after your initial post and 283 comments later and you’re still saving people from pulling their hair out! Only took me a 30mins or so to find your life saving post – thanks your help. Just a shame that 5 files including one CSS all sat at this not so magical number. Thanks again
December 22nd, 2009 at 16:11
Thanks Mike. Your post saved me hours of my life!!! Many thanks.
December 23rd, 2009 at 15:32
Great post – I have just had this issue in CS2 too – on a .php file. One other difference was that the file size *on disk* was 32768 bytes – a multiple of 8192 bytes – the file size was actually 29331 bytes. So I don’t think it matters which file size you look at.
December 23rd, 2009 at 15:48
Sorry – should have said CS3 in my last post – I don’t want to confuse matters!
December 23rd, 2009 at 16:02
I have also just noticed that the problem hasn’t been resolved either – must be something else!
I did the “fix” as described and was able to reopen the file in question. I could also view and select text at the top of the file, but when I scrolled down towards the bottom and then tried to select something, DW crashed. Adjusting the file size – even so that the *size on disk* is greater than 32768 bytes doesn’t make any difference.
There must be something wrong with the way that DW parses (and colour-codes) the code – but only in this particular file!
December 24th, 2009 at 13:40
Turns out that my problem was due to a corrupted cache file. See:
http://foundationphp.com/blog/2007/10/29/dreamweaver-crashes-apparently-caused-by-corrupted-cache-file/comment-page-2/
December 30th, 2009 at 4:27
Thanks Mike. Can’t believe this obscure bug, but even more amazing is the fact that I was able to find the fix so quickly thanks to you.
January 4th, 2010 at 5:26
Holy crap who woulda thunk. CS3 crashes out of no where and low and beholf, it’s this obscure bug! Thank you X 3.
January 4th, 2010 at 11:06
Its still happening in 2010. Not sure I would have found it without your help.
Many Thanks
January 9th, 2010 at 2:59
Thanks so much for this. I had renamed the folder as I suspected something like this, but having read this, it’ll save me going through my entire site eliminating the culprit.
January 11th, 2010 at 12:59
I had the same problem with CS4! But renaming fixed it. Thanks a lot!
January 12th, 2010 at 22:19
This is messed up. Nice fix. Thanks.
January 13th, 2010 at 6:05
Very helpful – thankyou so much.
January 13th, 2010 at 15:21
Wow, what an odd bug.. thankyou so much I found your site within a few minutes and I’m back up and running again! These things always happen when you’re busy, I was worried it would ruin my avo but yay it hasn’t :)
January 15th, 2010 at 17:41
Thanks! This website has been of great help! First result in Google, and immediately a winner :-)
January 21st, 2010 at 12:43
I too had this problem, and a few others like 1000’s of images in a directory crash DW; I rang Adobe and their solution was to use an external FTP client! Additionally they denied the above bug – perhaps it was a feature, for checking for files of this exact size – eg you know because DW has crashed!
January 22nd, 2010 at 6:14
thank you, thank you, thank you!
I thought i had a virus and it turns out it was this crazy bug!
cheers,
Shane
January 23rd, 2010 at 8:14
Simply amazing. I don’t usually leave thank-you notes but this was just too helpful not be recognized. Many, many thanks!
January 24th, 2010 at 1:54
Thank you! Thank you! Thank you!!!
Your 8,192 bytes fix worked like a charm!
January 25th, 2010 at 2:15
Thanks so much! I just had this happen to me, first time ever! I was so surprised that after a restart I still could not open it.
Thanks again!
January 26th, 2010 at 18:13
Thank you so much. In my case it was not a multiple of 8,192 bytes but just exactly half of it. I deleted the css file, and everything was ok again. Thanks to all.
January 30th, 2010 at 18:36
Jesus H. Christ, this worked.
Thanks!!
January 30th, 2010 at 18:40
Thank-you, thank-you, thank-you!
My css styles file had the dreadful byte count. Renamed the file to have a .txt ending, opened it up, added some temporary words at the bottom, changed the ending back to .css, and Dreamweaver is back.
Ghost in the machine, indeed.
February 2nd, 2010 at 20:56
Man, I’ve had this problem come up several times. Seems like about once a year the 8,182 byte bug rears its’ ugly head. CSS files always seem to for some reason cause this quirk. Luckily a quick search of “dreamweaver won’t start after crash” brought up your page.
Thanks!
February 5th, 2010 at 3:41
Tx for this – but I have another problem – my dreamweaver hangs when I exit the application – every time. It also happens with friends on mine (running on xp) so it can’t be vista vs xp.
Any solutions?
– Also – found that DW CS3 does not start up successfully if run on an Acer PC with Vista – you have to update the “Empowering Technology” and subaps to solve that problem.
February 5th, 2010 at 16:26
Sweet! Thanks a million for the help. First time I actually encountered this issue in over 3 years of DM. I wonder how the heck this actually causes issues with the startup?
February 7th, 2010 at 23:09
Thanks for posting about this issue, glad your post was the first to come up in my search! I just had this happen to me about 20 minutes ago. Turns out my file was exactly 3x that byte value. What a strange bug indeed!
Cheers and Thanks again :D
February 20th, 2010 at 14:02
This is so true! It still works :)
It occurs one every.. 5-6 months or something. Amazing. Good job documenting it!
February 22nd, 2010 at 13:00
Amazing! I was using CS3 and got the crash! I had rebooted, restored and as I have recently loaded DW CS4 (which loaded okay but I’m not currently using because the damn thing doesn’t have Layout Mode – but thats another story!) and having got that sinking feeling tried Google and your response was number 1 result. Looked for the errant CSSfile I was working on and sure enough – the magic number! Deleted a couple o fspaces and all loaded okay again.
I can’t believe its not been fixed by Adobe but there does seem to be a catalogue of poor coding since Adobe took over from Macromedia!
Thanks again.
February 23rd, 2010 at 11:35
bug confirmed…
thanks!
March 1st, 2010 at 13:09
Hi,
thanks for the post.
Had this happening twice today.
March 1st, 2010 at 15:22
Wow… this is such an odd bug. I just had to do a (non-destructive) reinstall of Windows due to some malware and my Dreamweaver had crashed beforehand which I attributed to the malware issues. When I reinstalled Dreamweaver this morning it would not load past the startup screen. I found this in Google while looking for reason for the lock up and I found that my index.shtml file was exactly 24,576 kb (3x 8,192kb). Opened it up in Notepad, deleted a couple lines and Dreamweaver opened right up. Thanks for saving me many hours, I had already done one uninstall and reinstall!
March 1st, 2010 at 19:28
awesome stupid bug, thank you so much for the soliutuion.
cheers
March 4th, 2010 at 4:38
Thank you so much for posting this problem and fix.
Just had this happen to me in the middle of a big job (aren’t they always?), and was not looking forward to harangueing Adobe or the other usual run arounds.
Guess they *STILL* haven’t fixed it yet!
(BTW, running DW CS3 on a HP Compaq 8710p with XP SP3.)
March 7th, 2010 at 7:54
I just encountered this problem as well –an odd one for sure! Thanks so much for the fix!! It worked exactly as you said it should :)
March 9th, 2010 at 10:27
That is the weirdest, weirdest thing. I barely believed you until I checked the file size of my CSS file… it’s like you were some kind of spooky mind reader. I added a simple space to one line and presto… fixed! Thanks a bunch :)
March 10th, 2010 at 18:28
Oh, how ridiculous. The EXACT same thing happened to me (except it was actually 8,762 bytes). I added some white space in Notepad, and voila — problem solved.
Thank you so much!