-
1. Re: Massive JS errors after today's update for CS6
Preran Jul 23, 2013 7:48 PM (in response to jefferis)Hi jefferis,
Sorry to hear about your problem and apologies for the inconvenience. I will check with the product team about what the problem could be.
Meanwhile, use this document to download CS6.
http://helpx.adobe.com/x-productkb/policy-pricing/cs6-product-downloads.html
Thanks,
Preran
-
2. Re: Massive JS errors after today's update for CS6
jefferis Jul 25, 2013 2:27 PM (in response to Preran)I reinstalled DW CS6 and it is working except that every time I try to update a page, it will save but is gives this warning:
Also, the latest updates yesterday, did not fix it. And Dreamweaver CC is TOTALLY unusable on my system.
With NO extensions installed it crashes on open every time:
Process: Dreamweaver [10122]
Path: /Applications/Adobe Dreamweaver CC/Adobe Dreamweaver CC.app/Contents/MacOS/Dreamweaver
Identifier: com.adobe.dreamweaver-13.0
Version: 13.0.0.6390 (13.0.0)
Code Type: X86 (Native)
Parent Process: launchd [316]
User ID: 501
Date/Time: 2013-07-25 17:21:51.182 -0400
OS Version: Mac OS X 10.8.4 (12E55)
Report Version: 10
Interval Since Last Report: 37493 sec
Crashes Since Last Report: 6
Per-App Interval Since Last Report: 1862 sec
Per-App Crashes Since Last Report: 7
Anonymous UUID: 8C5ABDFB-33A6-8E71-3744-4E67C3ADBE31
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
terminate called without an active exception
abort() called
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x0cebaa6a __pthread_kill + 10
1 libsystem_c.dylib 0x0cd76b2f pthread_kill + 101
2 libsystem_c.dylib 0x0cdad4ec abort + 168
3 libc++abi.dylib 0x0cc827e0 abort_message + 151
4 libc++abi.dylib 0x0cc80257 default_terminate() + 48
5 libstdc++.6.dylib 0x0c5744b2 std::terminate() + 21
6 com.adobe.dreamweaver-13.0 0x000c2baa TitanDocTemplate::OpenDocumentFile(unsigned short const*, CString, int, InitialDocFlag, unsigned long) + 7738
7 com.adobe.dreamweaver-13.0 0x000da91f TitanFrameManager::CreateFrame(CString const&, CString const&, InitialDocFlag, unsigned long) + 287
8 com.adobe.dreamweaver-13.0 0x000da1b8 TitanFrameManager::CreateFrame(CString const&, DocumentType::BaseType, unsigned long) + 72
9 com.adobe.dreamweaver-13.0 0x000ef745 TitanFrame::DoOpenFile(CString const&, unsigned long) + 821
10 com.adobe.dreamweaver-13.0 0x00b2415e StartPageOps::OnOpenDocument() + 110
11 com.adobe.dreamweaver-13.0 0x00b23db9 StartPageOps::OnMsgStartPageAction(unsigned int, long) + 233
12 com.adobe.dreamweaver-13.0 0x00b2488d StartPageView::OnMsgStartPageAction(unsigned int, long) + 61
13 com.adobe.dreamweaver-13.0 0x0119a3b1 CWnd::OnWndMsg(unsigned int, unsigned int, long, long*) + 353
14 com.adobe.dreamweaver-13.0 0x0119a21c CWnd::WindowProc(unsigned int, unsigned int, long) + 60
15 com.adobe.dreamweaver-13.0 0x0119825c CWnd::WinSendMessage(unsigned int, unsigned int, long) + 44
16 com.adobe.dreamweaver-13.0 0x0119b8d3 CPostedMessage::SpendTime() + 195
17 com.adobe.dreamweaver-13.0 0x0119b7d9 CPostedMessage::PostedMessageHandler(long const&) + 265
18 com.adobe.dreamweaver-13.0 0x0119b5dc CPostedMessage::HandlePostedMessages(bool) + 476
19 com.adobe.dreamweaver-13.0 0x011d43d2 CRealApp::DoPreEventProcessing(dvaui::ui::OS_Event const&) + 98
20 com.adobe.exo.framework 0x0467b1eb exo::app::AppBase::PreEventProcessing(dvaui::ui::OS_Event const&) + 27
21 com.adobe.exo.framework 0x04683eaa I
-
3. Re: Massive JS errors after today's update for CS6
SnakEyez02 Jul 25, 2013 3:47 PM (in response to jefferis)If you only re-installed that never solves the problems. For javascript errors you can try the following KB article. Start with #12 and #4 and go through the rest if necessary. Otherwise you need to run the CS Clean Tool.
http://helpx.adobe.com/dreamweaver/kb/troubleshoot-javascript-errors-dreamweaver-cs4.html
Also, if that KB article doesn't help, can you try booting up into a new OSX user account and confirm the problem happens in all accounts?




