Preran you were not able to solve my problem as you palmed me off to an advanced technician who asked me to preform the same tasks as I have been told to in the past and guess what?????? It STILL CRASHES ................
Do a crash dump... Do A Crash Dump......... DO A CRASH DUMP Which I did in the past and guess what???? No information was there to help solve the issue.....
Technicians say it is not OS nor APP dependant, well what is it, are you saying it is hardware related???
I have been told that I had to shut down my Firewall and/or antivirus, NOTHING CHANGES, it is not just my system (Obviously) as there are more people than me having the issues of Dreamweaver Crashing....
Adobe need to accept responsibility and FIX DREAMWEAVER!!!! IT IS APPLICATION DEPENDANT, it is ALWAYS DREAMWEAVER that is crashing yet the technicians at Adobe are too inept to find and fix the issue.
You continually ask the user who pays big bucks for the program, to be unpaid technicians/trouble-shooters.
We are all sick and tired of Adobe ripping the user off!!! it is simple Pay decent Technicians to find and really fix the problem(s).
It seems that there are several issues as for different people, as users are performing different tasks when the program crashes.
You need to reduce the monthly subscription fees as it is not fair that we pay the full price for a problematic program.
While I do not use other programs within the suite as much as Dreamweaver, they don't or haven't crashed as much as Dreamweaver does (if at all). So, it seems Dreamweaver is the main program that crashes.
I did a system report which contained the same information as a crash dump, yet you technician "Claimed" it was not enough information, and that only a crash dump would tell them what they needed to know, yet it hasn't in the past.
Stop making out you are trying to be helpful, and start actually being helpful - You sound like a politician - and I dislike Politicians! - You talk a lot but don't actually deal with the problems -
(You = Adobe Technicians)
You have blamed the actual HTML/CSS/JavaScript/PHP Code in the pages - No Errors Found - Still crashes
You have blamed the Antivirus Program - Antivirus is shut down - Still Crashes
You have blamed the Firewall - Firewall inactive - Still Crashes
You have blamed certain fonts - Removed all but standard windows Fonts - Still Crashes
You have blamed Lack of Ram - RAM exceeds minimum requirements (now 16 GB) - Still Crashes
You have blamed CPU - CPU Exceeds minimum requirements (Now 3.27 Ghz) - Still Crashes
You have blamed Low HDD space - HDD Exceeds minimum requirements (344 Gb free of 465 GB 74% Free) - Still Crashes
You have asked me to re-set the Dreamweaver Preferences - Still Crashes
You have asked me to un-install and re-install Dreamweaver - clicking on do not keep preferences on un-install - Still Crashes
You have asked me to un-install and re-install the entire Suite and don't keep any settings/preferences - Still Crashes
You have asked me to do a Crash Dump in all cases yet you could not find any relevant details and - Still Crashes
I have removed all traces of Adobe in the system registry after un-installation and re-installed suite - Still Crashes
This issue has been prevalent on Versions CS6, CC, CC2014 and CC2015 - Still Crashes
This issue has been prevalent across 4 versions of Windows XP, 7, 8.1, 10 (in my case) - it also appears to be an issue on Apple Computers as well - Still Crashes
This issue has been prevalent on 4 completely different computers (in my case) 4, 8, 16Gb RAM, 1.86. 2.14, 2.67, 3.27 GHz CPUs 250, 500 GB and 1 TB HDDs - Still crashes
One of your technicians lost a great deal of data when they took control of my system - Still Crashed
Even with no other programs open/running - Still Crashes
This is a list of all the garbage Adobe Technicians have suggested (that I can remember) and guess what???? IT STILL CRASHES
If you get the impression I am angry - you are correct with. And I feel my anger IS justified
If you get the impression that I am being somewhat "Blunt" with my comments - again you are correct - And I feel it is justified
If you get the impression that I doubt anyone at Adobe can fix the issue with their program - correct again and guess what??? Again I am justified - It has not been fixed since CS6