InDesign CS6 Causes System Crash
I installed the trial version of InDesign CS6, When I try to open Mini Bridge my System automatically crashes, I get the "Blue Screen of Death". I'm using Windows 7 Ultimate 64Bits. I need help, I'm afraid to open any other tool cuz' it could make my system crash again. Can someone help me?
Thank's.
What Bob is telling you is correct. The way operating systems and application programs work together is that the operating system “catches” any program errors or crashes and results in a “program error” message. Other applications continue to run and the integrity of the system is maintained.
A BSOD, Blue Screen of Death, is the result of either of the following:
(1) An unrecoverable hardware error occurs including problems with memory, disk drive, disk driver controller, video card, CPU, etc.
(2) A programming error occurs in the operating system itself from which the operating system cannot gracefully recover.
(3) A programming error occurs in system level components such as video drivers.
(4) Some combination of the above.
Adobe applications drive the video hardware and video drivers in ways that most other applications don't, often accessing the video card's GPU if the card has one. You may wish to check whether an updated video driver is available for your particular video card. If not, you may try reconfiguring your system to use the standard VGA driver and see if the crashes stop. If they do, then the video driver is the likely cause of the crashes. If the crashes continue you may want to have further diagnostics run on your system, especially memory diagnostics. InDesign does tend to use as much of the memory as you have up to 2GB or main memory. If you are running additional applications concurrent with InDesign, you may be exercising memory that isn't otherwise frequently accessed - and that memory may be problematic.
- Dov
Similar Messages
-
InDesign CS6 Text Tool Crashes App
As soon as I try to choose the text tool in InDesign CS6, it completely crashes (will included my entire crash log below)
I actually found this thread before starting mine.
http://forums.adobe.com/message/4798907#4798907
However that did not help me at all. Deleting the preferences is not a solution to my issue (was really hoping it would be that easy).
I am on an up to date Mountain Lion (10.8.2), Macbook Pro Retina.
I immediately checked out my Fonts, and nothing seems out of the ordinary. In fact this Macbook itself is a rather new acquisition, so I have the standards, the Adobe Fonts that come with CS5 & CS6, and exactly 3 fonts I have installed on my own (already tried disabling them in Font Book, still the same issue).
InDesign CS5 works no problems. It is only InDesign CS6. I just recently was able to get the CS6 Suite through work prior to the holidays, so this is the first time I have used InDesign CS6 since installing it.
I actually also manually went through all of my fonts, 1 by 1, and disabled any I did not need. I also Validated Fonts, found 14 issues, either disabled or removed the issues completely, validated them again, and no more issues. So really not sure what else I can do with my Fonts, they are more streamlined than they ever have been in the past.
So any and all ideas are welcome. I prefer to use the CS6 version since it was purchased and should work. TIA for any help offered.
Here is the entire Crash Log.
Process: Adobe InDesign CS6 [2535]
Path: /Applications/Adobe InDesign CS6/Adobe InDesign CS6.app/Contents/MacOS/Adobe InDesign CS6
Identifier: com.adobe.InDesign
Version: 8.0.1.406 (8010)
Code Type: X86 (Native)
Parent Process: launchd [137]
User ID: 502
Date/Time: 2013-01-08 10:27:28.824 -0500
OS Version: Mac OS X 10.8.2 (12C3006)
Report Version: 10
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
VM Regions Near 0:
--> __PAGEZERO 0000000000000000-0000000000001000 [ 4K] ---/--- SM=NUL /Applications/Adobe InDesign CS6/Adobe InDesign CS6.app/Contents/MacOS/Adobe InDesign CS6
__TEXT 0000000000001000-0000000000005000 [ 16K] r-x/rwx SM=COW /Applications/Adobe InDesign CS6/Adobe InDesign CS6.app/Contents/MacOS/Adobe InDesign CS6
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 ObjectModelLib.dylib 0x01600aa1 0x15d6000 + 174753
1 WidgetBinLib.dylib 0x00020b52 CPanelControlData::ReadWrite(IPMStream*, IDType<ImplementationID_tag>) + 132
2 com.adobe.InDesign.Widgets 0x160da359 MOwnerDrawDDCtrlData::MOwnerDrawDDCtrlData(IPMUnknown*) + 14231
3 PublicLib.dylib 0x017bb03c CreateObjectNoInit(IDataBase*, RsrcSpec const&, IDType<PMIID_tag>, IObjectModel const*) + 652
4 PublicLib.dylib 0x017bb140 CreateObject(IDataBase*, RsrcSpec const&, IDType<PMIID_tag>, IObjectModel const*) + 48
5 com.adobe.InDesign.Control Panel 0x1cc388fb 0x1cc2d000 + 47355
6 com.adobe.InDesign.Control Panel 0x1cc39036 0x1cc2d000 + 49206
7 com.adobe.InDesign.Control Panel 0x1cc397ab 0x1cc2d000 + 51115
8 com.adobe.InDesign.Control Panel 0x1cc3a953 0x1cc2d000 + 55635
9 com.adobe.InDesign.AppFramework 0x12192840 GetPlugIn + 33792
10 com.adobe.InDesign.AppFramework 0x121937f1 GetPlugIn + 37809
11 PublicLib.dylib 0x017ba06a CSubject::Change(IDType<ClassID_tag>, IDType<PMIID_tag> const&, void*) + 74
12 com.adobe.InDesign.Application UI 0x13b58aea 0x13b00000 + 363242
13 com.adobe.InDesign.Tool Box 0x1b411f16 GetPlugIn + 25270
14 com.adobe.InDesign.Actions 0x1b0f4bc4 GetPlugIn + 19908
15 com.adobe.InDesign.Actions 0x1b0e4044 0x1b0df000 + 20548
16 WidgetBinLib.dylib 0x000b2962 MDefaultEH::KeyboardShortcut(IEvent*) + 342
17 WidgetBinLib.dylib 0x000b21c4 CDefaultEH::KeyDown(IEvent*) + 68
18 WidgetBinLib.dylib 0x000b2b23 MDefaultEH::KeyDown(IEvent*) + 177
19 PublicLib.dylib 0x0171f2f7 CEventDispatcher::DispatchToEventHandlers(IEvent*) + 599
20 PublicLib.dylib 0x0171edb6 CEventDispatcher::DispatchEvent(IEvent*, IEvent::SystemHandledState) + 24
21 com.adobe.InDesign.Application UI 0x13b9ff94 GetPlugIn + 282340
22 com.adobe.InDesign.Application UI 0x13b9e2a0 GetPlugIn + 274928
23 com.apple.HIToolbox 0x94fa2b6b _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36
24 com.apple.HIToolbox 0x94e2a594 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1343
25 com.apple.HIToolbox 0x94e29980 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 430
26 com.apple.HIToolbox 0x94e3d855 SendEventToEventTarget + 88
27 com.apple.HIToolbox 0x94e5d8b2 ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 2392
28 com.apple.HIToolbox 0x94e2aa3f DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2538
29 com.apple.HIToolbox 0x94e29980 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 430
30 com.apple.HIToolbox 0x94e3d855 SendEventToEventTarget + 88
31 com.apple.HIToolbox 0x94e1f077 SendTSMEvent + 75
32 com.apple.HIToolbox 0x94e1eb0b SendUnicodeTextAEToUnicodeDoc + 745
33 com.apple.HIToolbox 0x94e1e704 TSMKeyEvent + 980
34 com.apple.HIToolbox 0x94e6e1e5 TSMProcessRawKeyEvent + 3102
35 com.apple.HIToolbox 0x94eaeec5 HandleCompatibilityKeyEvent + 323
36 com.apple.HIToolbox 0x94e26aba HIApplication::EventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 7318
37 com.apple.HIToolbox 0x94fa2b6b _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36
38 com.apple.HIToolbox 0x94e2a594 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1343
39 com.apple.HIToolbox 0x94e29980 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 430
40 com.apple.HIToolbox 0x94e297ca SendEventToEventTargetWithOptions + 94
41 com.apple.HIToolbox 0x94e5d38c ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 1074
42 com.apple.HIToolbox 0x94e2aa3f DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2538
43 com.apple.HIToolbox 0x94e29980 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 430
44 com.apple.HIToolbox 0x94e3d855 SendEventToEventTarget + 88
45 com.adobe.InDesign.AppFramework 0x1216f0dc 0x12160000 + 61660
46 com.adobe.InDesign.AppFramework 0x1218d329 GetPlugIn + 12009
47 com.adobe.InDesign 0x00001ec5 main + 341
48 com.adobe.InDesign 0x00001d55 start + 53
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x9168c9ae kevent + 10
1 libdispatch.dylib 0x925e0c71 _dispatch_mgr_invoke + 993
2 libdispatch.dylib 0x925e07a9 _dispatch_mgr_thread + 53
Thread 2:
0 libsystem_kernel.dylib 0x9168b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x972cb289 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x972cb512 pthread_cond_timedwait_relative_np + 47
3 com.apple.CoreServices.CarbonCore 0x9089f6ad TSWaitOnConditionTimedRelative + 177
4 com.apple.CoreServices.CarbonCore 0x907ebb9b MPWaitOnQueue + 261
5 PMRuntime.dylib 0x005b9581 SetVSizeBaseline(unsigned long) + 1473
6 com.apple.CoreServices.CarbonCore 0x90872a7b PrivateMPEntryPoint + 68
7 libsystem_c.dylib 0x972c6557 _pthread_start + 344
8 libsystem_c.dylib 0x972b0cee thread_start + 34
Thread 3:
0 libsystem_kernel.dylib 0x9168c0ee __workq_kernreturn + 10
1 libsystem_c.dylib 0x972c904c _pthread_workq_return + 45
2 libsystem_c.dylib 0x972c8e19 _pthread_wqthread + 448
3 libsystem_c.dylib 0x972b0cca start_wqthread + 30
Thread 4:
0 libsystem_kernel.dylib 0x9168c0ee __workq_kernreturn + 10
1 libsystem_c.dylib 0x972c904c _pthread_workq_return + 45
2 libsystem_c.dylib 0x972c8e19 _pthread_wqthread + 448
3 libsystem_c.dylib 0x972b0cca start_wqthread + 30
Thread 5:
0 libsystem_kernel.dylib 0x9168c0ee __workq_kernreturn + 10
1 libsystem_c.dylib 0x972c904c _pthread_workq_return + 45
2 libsystem_c.dylib 0x972c8e19 _pthread_wqthread + 448
3 libsystem_c.dylib 0x972b0cca start_wqthread + 30
Thread 6:
0 libsystem_kernel.dylib 0x916897d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x91688cb0 mach_msg + 68
2 com.apple.CoreServices.CarbonCore 0x9089c35b TS_exception_listener_thread + 89
3 libsystem_c.dylib 0x972c6557 _pthread_start + 344
4 libsystem_c.dylib 0x972b0cee thread_start + 34
Thread 7:
0 libsystem_kernel.dylib 0x9168b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x972cb220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x973510a1 pthread_cond_wait$UNIX2003 + 71
3 com.apple.CoreServices.CarbonCore 0x9089f492 TSWaitOnCondition + 128
4 com.apple.CoreServices.CarbonCore 0x9089f68e TSWaitOnConditionTimedRelative + 146
5 com.apple.CoreServices.CarbonCore 0x907ebb9b MPWaitOnQueue + 261
6 com.adobe.ACE 0x00607a69 0x5c8000 + 260713
7 com.adobe.ACE 0x00606d99 0x5c8000 + 257433
8 com.apple.CoreServices.CarbonCore 0x90872a7b PrivateMPEntryPoint + 68
9 libsystem_c.dylib 0x972c6557 _pthread_start + 344
10 libsystem_c.dylib 0x972b0cee thread_start + 34
Thread 8:
0 libsystem_kernel.dylib 0x9168b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x972cb220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x973510a1 pthread_cond_wait$UNIX2003 + 71
3 com.apple.CoreServices.CarbonCore 0x9089f492 TSWaitOnCondition + 128
4 com.apple.CoreServices.CarbonCore 0x9089f68e TSWaitOnConditionTimedRelative + 146
5 com.apple.CoreServices.CarbonCore 0x907ebb9b MPWaitOnQueue + 261
6 com.adobe.ACE 0x00607a69 0x5c8000 + 260713
7 com.adobe.ACE 0x00606d99 0x5c8000 + 257433
8 com.apple.CoreServices.CarbonCore 0x90872a7b PrivateMPEntryPoint + 68
9 libsystem_c.dylib 0x972c6557 _pthread_start + 344
10 libsystem_c.dylib 0x972b0cee thread_start + 34
Thread 9:
0 libsystem_kernel.dylib 0x9168b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x972cb220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x973510a1 pthread_cond_wait$UNIX2003 + 71
3 com.apple.CoreServices.CarbonCore 0x9089f492 TSWaitOnCondition + 128
4 com.apple.CoreServices.CarbonCore 0x9089f68e TSWaitOnConditionTimedRelative + 146
5 com.apple.CoreServices.CarbonCore 0x907ebb9b MPWaitOnQueue + 261
6 com.adobe.ACE 0x00607a69 0x5c8000 + 260713
7 com.adobe.ACE 0x00606d99 0x5c8000 + 257433
8 com.apple.CoreServices.CarbonCore 0x90872a7b PrivateMPEntryPoint + 68
9 libsystem_c.dylib 0x972c6557 _pthread_start + 344
10 libsystem_c.dylib 0x972b0cee thread_start + 34
Thread 10:
0 libsystem_kernel.dylib 0x9168b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x972cb220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x973510a1 pthread_cond_wait$UNIX2003 + 71
3 com.apple.CoreServices.CarbonCore 0x9089f492 TSWaitOnCondition + 128
4 com.apple.CoreServices.CarbonCore 0x9089f68e TSWaitOnConditionTimedRelative + 146
5 com.apple.CoreServices.CarbonCore 0x907ebb9b MPWaitOnQueue + 261
6 com.adobe.ACE 0x00607a69 0x5c8000 + 260713
7 com.adobe.ACE 0x00606d99 0x5c8000 + 257433
8 com.apple.CoreServices.CarbonCore 0x90872a7b PrivateMPEntryPoint + 68
9 libsystem_c.dylib 0x972c6557 _pthread_start + 344
10 libsystem_c.dylib 0x972b0cee thread_start + 34
Thread 11:
0 libsystem_kernel.dylib 0x9168b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x972cb220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x973510a1 pthread_cond_wait$UNIX2003 + 71
3 com.apple.CoreServices.CarbonCore 0x9089f492 TSWaitOnCondition + 128
4 com.apple.CoreServices.CarbonCore 0x9089f68e TSWaitOnConditionTimedRelative + 146
5 com.apple.CoreServices.CarbonCore 0x907ebb9b MPWaitOnQueue + 261
6 com.adobe.ACE 0x00607a69 0x5c8000 + 260713
7 com.adobe.ACE 0x00606d99 0x5c8000 + 257433
8 com.apple.CoreServices.CarbonCore 0x90872a7b PrivateMPEntryPoint + 68
9 libsystem_c.dylib 0x972c6557 _pthread_start + 344
10 libsystem_c.dylib 0x972b0cee thread_start + 34
Thread 12:
0 libsystem_kernel.dylib 0x9168b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x972cb220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x973510a1 pthread_cond_wait$UNIX2003 + 71
3 com.apple.CoreServices.CarbonCore 0x9089f492 TSWaitOnCondition + 128
4 com.apple.CoreServices.CarbonCore 0x9089f68e TSWaitOnConditionTimedRelative + 146
5 com.apple.CoreServices.CarbonCore 0x907ebb9b MPWaitOnQueue + 261
6 com.adobe.ACE 0x00607a69 0x5c8000 + 260713
7 com.adobe.ACE 0x00606d99 0x5c8000 + 257433
8 com.apple.CoreServices.CarbonCore 0x90872a7b PrivateMPEntryPoint + 68
9 libsystem_c.dylib 0x972c6557 _pthread_start + 344
10 libsystem_c.dylib 0x972b0cee thread_start + 34
Thread 13:
0 libsystem_kernel.dylib 0x9168b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x972cb220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x973510a1 pthread_cond_wait$UNIX2003 + 71
3 com.apple.CoreServices.CarbonCore 0x9089f492 TSWaitOnCondition + 128
4 com.apple.CoreServices.CarbonCore 0x9089f68e TSWaitOnConditionTimedRelative + 146
5 com.apple.CoreServices.CarbonCore 0x907ebb9b MPWaitOnQueue + 261
6 com.adobe.ACE 0x00607a69 0x5c8000 + 260713
7 com.adobe.ACE 0x00606d99 0x5c8000 + 257433
8 com.apple.CoreServices.CarbonCore 0x90872a7b PrivateMPEntryPoint + 68
9 libsystem_c.dylib 0x972c6557 _pthread_start + 344
10 libsystem_c.dylib 0x972b0cee thread_start + 34
Thread 14:
0 libsystem_kernel.dylib 0x9168b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x972cb220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x973510a1 pthread_cond_wait$UNIX2003 + 71
3 com.adobe.InDesign.AppFramework 0x12260556 GetPlugIn + 876822
4 com.adobe.InDesign.AppFramework 0x1225c772 GetPlugIn + 860978
5 com.adobe.InDesign.AppFramework 0x1225d3c5 GetPlugIn + 864133
6 com.adobe.InDesign.AppFramework 0x1225e98e GetPlugIn + 869710
7 com.adobe.InDesign.AppFramework 0x1225e9fa GetPlugIn + 869818
8 com.adobe.InDesign.AppFramework 0x1225ea66 GetPlugIn + 869926
9 com.adobe.boost_threads.framework 0x01c6840d thread_proxy + 141
10 libsystem_c.dylib 0x972c6557 _pthread_start + 344
11 libsystem_c.dylib 0x972b0cee thread_start + 34
Thread 15:
0 libsystem_kernel.dylib 0x9168b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x972cb220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x973510a1 pthread_cond_wait$UNIX2003 + 71
3 com.adobe.InDesign.AppFramework 0x12260556 GetPlugIn + 876822
4 com.adobe.InDesign.AppFramework 0x1225c772 GetPlugIn + 860978
5 com.adobe.InDesign.AppFramework 0x1225d3c5 GetPlugIn + 864133
6 com.adobe.InDesign.AppFramework 0x1225e98e GetPlugIn + 869710
7 com.adobe.InDesign.AppFramework 0x1225e9fa GetPlugIn + 869818
8 com.adobe.InDesign.AppFramework 0x1225ea66 GetPlugIn + 869926
9 com.adobe.boost_threads.framework 0x01c6840d thread_proxy + 141
10 libsystem_c.dylib 0x972c6557 _pthread_start + 344
11 libsystem_c.dylib 0x972b0cee thread_start + 34
Thread 16:
0 libsystem_kernel.dylib 0x9168bc72 __semwait_signal + 10
1 libsystem_c.dylib 0x97350a61 nanosleep$UNIX2003 + 189
2 com.adobe.InDesign.Support for JavaScript 0x18226acb GetPlugIn + 317883
3 com.adobe.InDesign.Support for JavaScript 0x1820bf79 GetPlugIn + 208489
4 com.adobe.InDesign.Support for JavaScript 0x18226e38 GetPlugIn + 318760
5 libsystem_c.dylib 0x972c6557 _pthread_start + 344
6 libsystem_c.dylib 0x972b0cee thread_start + 34
Thread 17:
0 libsystem_kernel.dylib 0x9168bb3e __recvfrom + 10
1 libsystem_c.dylib 0x97350bcb recv$UNIX2003 + 54
2 ServiceManager-Launcher.dylib 0x1f33f733 Invoke + 47867
3 ServiceManager-Launcher.dylib 0x1f33e846 Invoke + 44046
4 ServiceManager-Launcher.dylib 0x1f33d988 Invoke + 40272
5 ServiceManager-Launcher.dylib 0x1f33da0f Invoke + 40407
6 ServiceManager-Launcher.dylib 0x1f338baf Invoke + 20343
7 ServiceManager-Launcher.dylib 0x1f338ea7 Invoke + 21103
8 ServiceManager-Launcher.dylib 0x1f339685 Invoke + 23117
9 ServiceManager-Launcher.dylib 0x1f3398f9 Invoke + 23745
10 ServiceManager-Launcher.dylib 0x1f33c2a0 Invoke + 34408
11 ServiceManager-Launcher.dylib 0x1f33c3fd Invoke + 34757
12 ServiceManager-Launcher.dylib 0x1f33cc91 Invoke + 36953
13 ServiceManager-Launcher.dylib 0x1f33cdb2 Invoke + 37242
14 ServiceManager-Launcher.dylib 0x1f32f656 Login + 461
15 ServiceManager-Launcher.dylib 0x1f33309a Login + 15377
16 ServiceManager-Launcher.dylib 0x1f33d165 Invoke + 38189
17 ServiceManager-Launcher.dylib 0x1f33f2eb Invoke + 46771
18 libsystem_c.dylib 0x972c6557 _pthread_start + 344
19 libsystem_c.dylib 0x972b0cee thread_start + 34
Thread 18:: com.apple.CFSocket.private
0 libsystem_kernel.dylib 0x9168bbe6 __select + 10
1 com.apple.CoreFoundation 0x98905c00 __CFSocketManager + 1632
2 libsystem_c.dylib 0x972c6557 _pthread_start + 344
3 libsystem_c.dylib 0x972b0cee thread_start + 34
Thread 19:
0 libsystem_kernel.dylib 0x9168c0ee __workq_kernreturn + 10
1 libsystem_c.dylib 0x972c904c _pthread_workq_return + 45
2 libsystem_c.dylib 0x972c8e19 _pthread_wqthread + 448
3 libsystem_c.dylib 0x972b0cca start_wqthread + 30
Thread 20:
0 libsystem_kernel.dylib 0x9168b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x972cb220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x973510a1 pthread_cond_wait$UNIX2003 + 71
3 com.adobe.ape.engine 0x26ab804f APXGetHostAPI + 2633743
4 com.adobe.ape.engine 0x2684962f APXGetHostAPI + 83439
5 com.adobe.ape.engine 0x26ab813e APXGetHostAPI + 2633982
6 com.adobe.ape.engine 0x26ab81a7 APXGetHostAPI + 2634087
7 com.adobe.ape.engine 0x26ab82c6 APXGetHostAPI + 2634374
8 libsystem_c.dylib 0x972c6557 _pthread_start + 344
9 libsystem_c.dylib 0x972b0cee thread_start + 34
Thread 21:
0 libsystem_kernel.dylib 0x9168b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x972cb220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x973510a1 pthread_cond_wait$UNIX2003 + 71
3 com.adobe.ape.engine 0x26ab804f APXGetHostAPI + 2633743
4 com.adobe.ape.engine 0x2684962f APXGetHostAPI + 83439
5 com.adobe.ape.engine 0x26ab813e APXGetHostAPI + 2633982
6 com.adobe.ape.engine 0x26ab81a7 APXGetHostAPI + 2634087
7 com.adobe.ape.engine 0x26ab82c6 APXGetHostAPI + 2634374
8 libsystem_c.dylib 0x972c6557 _pthread_start + 344
9 libsystem_c.dylib 0x972b0cee thread_start + 34
Thread 22:
0 libsystem_kernel.dylib 0x9168b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x972cb220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x973510a1 pthread_cond_wait$UNIX2003 + 71
3 com.adobe.ape.engine 0x26ab804f APXGetHostAPI + 2633743
4 com.adobe.ape.engine 0x2684962f APXGetHostAPI + 83439
5 com.adobe.ape.engine 0x26ab813e APXGetHostAPI + 2633982
6 com.adobe.ape.engine 0x26ab81a7 APXGetHostAPI + 2634087
7 com.adobe.ape.engine 0x26ab82c6 APXGetHostAPI + 2634374
8 libsystem_c.dylib 0x972c6557 _pthread_start + 344
9 libsystem_c.dylib 0x972b0cee thread_start + 34
Thread 23:
0 libsystem_kernel.dylib 0x9168b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x972cb220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x973510a1 pthread_cond_wait$UNIX2003 + 71
3 com.adobe.ape.engine 0x26ab804f APXGetHostAPI + 2633743
4 com.adobe.ape.engine 0x2684962f APXGetHostAPI + 83439
5 com.adobe.ape.engine 0x26ab813e APXGetHostAPI + 2633982
6 com.adobe.ape.engine 0x26ab81a7 APXGetHostAPI + 2634087
7 com.adobe.ape.engine 0x26ab82c6 APXGetHostAPI + 2634374
8 libsystem_c.dylib 0x972c6557 _pthread_start + 344
9 libsystem_c.dylib 0x972b0cee thread_start + 34
Thread 24:
0 libsystem_kernel.dylib 0x9168b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x972cb289 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x972cb512 pthread_cond_timedwait_relative_np + 47
3 com.adobe.ape.engine 0x26ab7f59 APXGetHostAPI + 2633497
4 com.adobe.ape.engine 0x268a814c APXGetHostAPI + 471308
5 com.adobe.ape.engine 0x268a819a APXGetHostAPI + 471386
6 com.adobe.ape.engine 0x26ab813e APXGetHostAPI + 2633982
7 com.adobe.ape.engine 0x26ab81a7 APXGetHostAPI + 2634087
8 com.adobe.ape.engine 0x26ab82c6 APXGetHostAPI + 2634374
9 libsystem_c.dylib 0x972c6557 _pthread_start + 344
10 libsystem_c.dylib 0x972b0cee thread_start + 34
Thread 25:: com.apple.NSURLConnectionLoader
0 libsystem_kernel.dylib 0x916897d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x91688cb0 mach_msg + 68
2 com.apple.CoreFoundation 0x988bc599 __CFRunLoopServiceMachPort + 185
3 com.apple.CoreFoundation 0x988c1f7f __CFRunLoopRun + 1247
4 com.apple.CoreFoundation 0x988c163a CFRunLoopRunSpecific + 378
5 com.apple.CoreFoundation 0x988c14ab CFRunLoopRunInMode + 123
6 com.apple.Foundation 0x9786313a +[NSURLConnection(Loader) _resourceLoadLoop:] + 395
7 com.apple.Foundation 0x978c71d8 -[NSThread main] + 45
8 com.apple.Foundation 0x978c715b __NSThread__main__ + 1396
9 libsystem_c.dylib 0x972c6557 _pthread_start + 344
10 libsystem_c.dylib 0x972b0cee thread_start + 34
Thread 26:
0 libsystem_kernel.dylib 0x9168b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x972cb289 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x972cb512 pthread_cond_timedwait_relative_np + 47
3 com.adobe.ape.engine 0x26ab8017 APXGetHostAPI + 2633687
4 com.adobe.ape.engine 0x26ad120e APXGetHostAPI + 2736590
5 com.adobe.ape.engine 0x26ab813e APXGetHostAPI + 2633982
6 com.adobe.ape.engine 0x26ab81a7 APXGetHostAPI + 2634087
7 com.adobe.ape.engine 0x26ab82c6 APXGetHostAPI + 2634374
8 libsystem_c.dylib 0x972c6557 _pthread_start + 344
9 libsystem_c.dylib 0x972b0cee thread_start + 34
Thread 27:
0 libsystem_kernel.dylib 0x9168b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x972cb289 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x972cb512 pthread_cond_timedwait_relative_np + 47
3 com.adobe.ape.engine 0x26ab8017 APXGetHostAPI + 2633687
4 com.adobe.ape.engine 0x26c460c8 APXGetHostAPI + 4264072
5 com.adobe.ape.engine 0x26ab813e APXGetHostAPI + 2633982
6 com.adobe.ape.engine 0x26ab81a7 APXGetHostAPI + 2634087
7 com.adobe.ape.engine 0x26ab82c6 APXGetHostAPI + 2634374
8 libsystem_c.dylib 0x972c6557 _pthread_start + 344
9 libsystem_c.dylib 0x972b0cee thread_start + 34
Thread 28:
0 libsystem_kernel.dylib 0x9168b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x972cb289 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x972cb512 pthread_cond_timedwait_relative_np + 47
3 com.adobe.ape.engine 0x26ab8017 APXGetHostAPI + 2633687
4 com.adobe.ape.engine 0x26c460c8 APXGetHostAPI + 4264072
5 com.adobe.ape.engine 0x26ab813e APXGetHostAPI + 2633982
6 com.adobe.ape.engine 0x26ab81a7 APXGetHostAPI + 2634087
7 com.adobe.ape.engine 0x26ab82c6 APXGetHostAPI + 2634374
8 libsystem_c.dylib 0x972c6557 _pthread_start + 344
9 libsystem_c.dylib 0x972b0cee thread_start + 34
Thread 29:
0 libsystem_kernel.dylib 0x9168b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x972cb220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x973510a1 pthread_cond_wait$UNIX2003 + 71
3 MultiProcessor Support 0x2a6edeac boost::condition_variable::wait(boost::unique_lock<boost::mutex>&) + 140
4 MultiProcessor Support 0x2a6d1513 ThreadFunctor::operator()() + 99
5 MultiProcessor Support 0x2a6d125a boost::detail::thread_data<ThreadFunctor>::run() + 22
6 MultiProcessor Support 0x2a6ed547 thread_proxy + 167
7 libsystem_c.dylib 0x972c6557 _pthread_start + 344
8 libsystem_c.dylib 0x972b0cee thread_start + 34
Thread 30:
0 libsystem_kernel.dylib 0x9168b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x972cb220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x973510a1 pthread_cond_wait$UNIX2003 + 71
3 MultiProcessor Support 0x2a6edeac boost::condition_variable::wait(boost::unique_lock<boost::mutex>&) + 140
4 MultiProcessor Support 0x2a6d1513 ThreadFunctor::operator()() + 99
5 MultiProcessor Support 0x2a6d125a boost::detail::thread_data<ThreadFunctor>::run() + 22
6 MultiProcessor Support 0x2a6ed547 thread_proxy + 167
7 libsystem_c.dylib 0x972c6557 _pthread_start + 344
8 libsystem_c.dylib 0x972b0cee thread_start + 34
Thread 31:
0 libsystem_kernel.dylib 0x9168b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x972cb220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x973510a1 pthread_cond_wait$UNIX2003 + 71
3 MultiProcessor Support 0x2a6edeac boost::condition_variable::wait(boost::unique_lock<boost::mutex>&) + 140
4 MultiProcessor Support 0x2a6d1513 ThreadFunctor::operator()() + 99
5 MultiProcessor Support 0x2a6d125a boost::detail::thread_data<ThreadFunctor>::run() + 22
6 MultiProcessor Support 0x2a6ed547 thread_proxy + 167
7 libsystem_c.dylib 0x972c6557 _pthread_start + 344
8 libsystem_c.dylib 0x972b0cee thread_start + 34
Thread 32:
0 libsystem_kernel.dylib 0x9168b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x972cb220 _pthread_cond_wait + 833
2 libsystem_Hi Bob
We're actually using your Lynda tutorial for our training, it's such a great resource thank you.
Here's a thread I was reading which wasn't helpful for myself although I did try some solutions that were relevant to me.
Re: InDesign CS 6 Folio Builder crashing
Solutions tried:
- Re installing InDesign CS6
- Downloaded DPS updates directly from Adobe
- One post suggested deleting my cache file/folders which would result in any folios I've made deleted however this
is the first time I've used the DPS tools in Adobe so I didn't worry.
- I've also deleted/reset my preferences
Is there anything else you can suggest? -
Please help, InDesign CS6 (cloud) keeps crashing on OS 10.8.2
It happens after I open a file and try do just about anything, modify a photo, add text, move an object, the most basic tasks on simple one-page documents. I've tried all the recommendations I can find including verifying fonts, deleting preferences, checking for updates, etc. and though I've tried all those things, InDesign still won't allow me to do anything. I've spent all day trying to troubleshoot and I have I'm desperate to get it working. I have two major deadlines. Any help you can provide would be extremely appreciated!
Let us know how you make out.
Bob
mackeys <mailto:[email protected]>
Monday, April 1, 2013 3:21 PM
>
Re: Please help, InDesign CS6 (cloud) keeps crashing on OS 10.8.2
created by mackeys <http://forums.adobe.com/people/mackeys> in
/InDesign/ - View the full discussion
<http://forums.adobe.com/message/5196905#5196905 -
Indesign cs6 is continuously crashing
Indesign cs6 is continuously crashing when trying to place an image. help!
yes you're right! Just did a test right now. And it is that nasty bugger of an image! Thanks for the tip!
-
InDesign CS6 (CC edition) crashes on save/export
I'm having trouble with InDesign CS6 crashing every single time I attempt to save or export a document I just finished. It has never been saved before, other documents save and close fine, I've tried removing all the links from the file, and it still crashes on save. I've tried copying it, and the moment I tell it to place the document on the clipboard it crashes. I don't know what else could POSSIBLY be causing this crash. There is no crash or error reports.
And you know what, Peter? If the Sync guys were giving us the same level of care and compassion you are, I'd wouldn't be even a fraction as upset. But we're told to hold sync in one hand, their rhetoric in the other, and see which fills up first. Adobe should hire you for PR, because THIS is the kind of customer service I want to see out of a company charging multiple thousands of dollars for its products. As for sync, I understand the dev time, but why pull down the beta when it was still functioning? Why ignore the public that is asking simply for help making business decisions? As you said, you don't do it for business but you DO rely on it, so you can understand where even if we don't like the answers, we need to hear SOMETHING, we need to at least know the scope of the timetable we're looking at. Are we looking at a few weeks, a few months, or a year or two?
Telling people who are locked in a contract with adobe to utilize a different product for sync is like me buying a toaster and being told, when it doesn't work, to just go use a skillet. Yes it can do the job, and had I wanted it to do the job I never would have bought a toaster. But I wanted a toaster. I was offered a toaster. Most importantly I paid for a toaster and am still paying a protection plan for it, but when it doesn't work I'm told "Oh, we know. We're making a new toaster, so we turned off all the old toasters. When we finish our new toaster you'll recieve one of our brand new toasters." and while that scenario doesn't sound completely implausible, as there have been recalls in the past, instead of becoming irate that our perfectly functional toasters were turned off, we simply asked "well how long?" and we were told a month. So we waited 5 weeks, and said "Ok guys, your new toasters should be here by now. What gives?" and were replied to with "Oh, well thank you for your patience, but we've got another couple weeks on your toasters." now it's been two months, and still no toaster. Sure it's a Sony toaster. Sony's never made toasters before. But sony having never made toasters before is no excuse for locking people into a contract on the promise of a toaster, then you turned off their toaster, and just keep promising "the toaster's in the mail" Adobe may not have ever done cloud sync software before, but they HAVE done marketing, business to business relationships, and customer service. Saying they don't know about sync programs is a non starter argument, because they are failing in areas they've been engaged in for YEARS. I may not know a THING about software development, but I know you don't just tell your paying customers to sit on it and wait until it's done without any idea of when that will be, PARTICULARLY when doing so puts you in breech of contract. -
Indesign CS6 just started crashing when exporting to pdf - help?
I just got Indesign CS6 a few weeks ago and I'm using it on a new macbook pro. I had exported to pdf a few times with no problem. Today, I tried the same thing and Indesign began quitting for no apparent reason. I already tried restarting my computer. Any suggestions?
Hmmm...maybe I should try that. InDesign causes Acrobat to crash about half the time when I export it out as an Interactive PDF. The only thing is, it has always happened on all my ID files and it happens sporadically. If it crashes, I just do it once or twice again and it works. That would be the only reason I wouldn't think this will be my issue.
I'll go through the process a few times and see what happens...thanks. -
Webcam Live Pro causes system crash with Windows XP Home
Ever since installing Webcam Live Pro I have been having random system restarts. This ONLY happens when the webcam is being used. It happens when using the Creative Webcam Center or another application. Sometimes the restart will happen after a few minutes, and other times an hour or more. I am running Windows XP sp2 with all patches, and there are no driver conflicts listed in Device Manager. I have the cam set at 60 hz.
Even though there are no listed driver conflicts in Device Manager, there clearly is a driver conflict that occurs from time to time. I have read of other people having this same problem on this forum with Webcam Live Pro. I am using the driver ...0 which is dated 0//2004, and the automatic update program on this web site says that I am using the latest driver. But in the download section of this web site, the latest driver is listed as .0.0.0 and dated November 9, 2004. The driver numbers or dates do not match, and the driver on the web seems to have an earlier number but a later date!?
Does anyone (especially a Creative tech support person who may be reading this post) have any idea what to do? The driver version is one issue. But the big issue is the system crashes.
Best,
CBSolution! I discovered the problem causing the system crash, and I think it is sufficiently interesting to note here so that others may benefit from what I discovered. First, there is no fundamental problem/conflict with the driver for Webcam Live Pro. The trouble in my instance is that I was running another program that utilized the web cam, and that program conflicted with the Webcam Live Pro program that was constantly running in the system tray. Basically, the program in the system tray is loaded with the set-up for Webcam Live Pro. It constantly monitors the computer system to see if the cam is connected to the computer. When it does this while another program is using the cam, the conflict occurs, causing the entire computer to reboot. The solution is to right mouse click the icon for Webcam Live Pro in the system tray, go to settings, and to remove the check that allows the program to check for the presence of the web cam. Just to be safe, I then also exited the Webcam Live Pro program from the system tray so that nothing from that program could interfere with my use of the webcam using another program.
The result is that the webcam is rock solid, with no system crashes. I have been running it nonstop for hours without a problem.
I hope this helps someone else.
Best,
CB -
About every two months I have to uninstal and reinstal InDesign. It will crash when I open it and won't open again until I uninstal it and the reinstal it and then It'll work for roughly two months before I have to do it again. I had this problem with CS6 and CC. And it's only on the Mac osX 10.8. The Windows 7 runs great.
Does anyone else have this problem?
Is there a fix?
Does Adobe know about the problem?Normal I'd take that answer, but I don't think that's it. I have a 2010 MacBook Air with CC it's crashing on, at school last year my 2009 iMac had the same problem with CS6 and at work my brand new (bought last month) iMac has the problem with CS6. I don't think that it's a program conflict, the only software all three have in common are Adobe and Apple's stock programs: iMovie, Garageband, etc.
-
MDNSReporter causing system crash
Ever since upgrading to 10.5.7, I've had frequent, daily system crashes. I did an archive and install from the disks, then used the combo updater to 10.5.7. The console logs show that just prior to every crash, I have a lot of activity regarding the mDNSReporter for a few seconds. Any suggestions on what might be causing this? Currently I think it may be Little Snitch (2.1.4) interacting with something else, so i plan to disable it for a while and see if I stop crashing. Logs are posted below.
6/6/09 11:39:00 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:00 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:00 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:01 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:01 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:01 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:01 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:02 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:02 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:02 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:03 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:03 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:03 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:04 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:04 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:04 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:05 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:05 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:05 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:06 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:06 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:06 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:07 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:07 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:08 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:08 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:08 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:09 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:09 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:09 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:10 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:10 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:10 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:11 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:11 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:12 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:12 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:12 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:13 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:13 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:13 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:14 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:14 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:14 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:14 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:15 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:15 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:15 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:16 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:16 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:16 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:17 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:17 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:17 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:17 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:18 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:18 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:19 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:19 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:19 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:20 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:20 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:20 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:21 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:21 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:21 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:22 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:22 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:22 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:23 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:23 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:23 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)
6/6/09 11:39:24 AM mDNSResponder[16] CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for NAT-PMP announcements
6/6/09 11:39:24 AM mDNSResponder[16] mDNSPlatformUDPSocket: SetupSocket 5350 failed error -1 errno 48 (Address already in use)Shams Shirley,
The link you gave points directly to the one I gave you.
If you follow [the link I gave you|http://openradar.appspot.com/radar?id=3406], you'll see that it gives a diff to apply as a workaround. One other way to make the problem in mDNSReporter go away is to put your Mac on the internet side of your router.
You should know that [portmap|http://developer.apple.com/documentation/Darwin/Reference/ManPages/man8/portmap .8.html] is built into OS X, as is the [kill|http://developer.apple.com/documentation/Darwin/Reference/ManPages/man1/kill.1. html] command.
Yes, finding and removing the conflicting app that opens up UDP ALL-SYSTEMS.MCAST.NET:5350 with SO_REUSEPORT would take care of the issue. What do you see when you run [netstat|http://developer.apple.com/documentation/Darwin/Reference/ManPages/man1/netstat .1.html] with the -g (multicast) switch?
-Wayne -
InDesign CS6 Folio Builder Crashes Version 32.0.0
Hi,
I've only just installed the DPS Desktop Tools for InDesign CS6 and the installation worked perfectly although upon opening Folio Builder in InDesign it results in the program crashing...
So far I've re installed InDesign I've tried a few other solutions although none seem to be relevant to this version 32.0.0
It wouldn't be that big a deal although I need the Folio Builder tool for my current assessment.. Not being able to work on it at home is going to be detrimental to the end result
Hope someone can help me!Hi Bob
We're actually using your Lynda tutorial for our training, it's such a great resource thank you.
Here's a thread I was reading which wasn't helpful for myself although I did try some solutions that were relevant to me.
Re: InDesign CS 6 Folio Builder crashing
Solutions tried:
- Re installing InDesign CS6
- Downloaded DPS updates directly from Adobe
- One post suggested deleting my cache file/folders which would result in any folios I've made deleted however this
is the first time I've used the DPS tools in Adobe so I didn't worry.
- I've also deleted/reset my preferences
Is there anything else you can suggest? -
InDesign CS6 crashed when I was editing hyperlinks in a book. When I reopened the program, instead of 9 chapter files, I have 45 and all are untitled. What should I do ? Open the files from my most recently saved chapter files? Create a new indb file?
When you restart after a crash ID uses the recovery data to attempt to rebuild all the files that were open when the program crashed, but it will do this as untitled copies for safety.
You can open the last saved version of any file that was open most times, too, unless the crash occured during a write operation and damaged the file. My tendency is to do a save as to a new name on the recovered files and not overwtite the originals, just in case, but that can be problematic if you have inter-file cross-references. You should be able to either make a new book file, or replace individual documents in the existing book with the new versions. -
Satellite L655 - RAM upgrade causes system crash
I bought and inserted 2 4GB Kingston RAM chips. When I boot up the Windows and Ubuntu 14.04 (I have a dual boot system) crashes.
If I run a memory test from Ubuntu's boot menu the system freezes.
I put back the old RAM and all is well.
To solve this problem I tried upgrading the BIOS firmware using the software available from the Toshiba site, but that gives me an error saying that the battery needs to be fully charged and the AC adapter plugged in. Fully charged battery with charger plugged in still gives the same error. I replaced the battery, which was old and only lasted 5 minutes, but the error remains on the bios upgrade.
Any ideas what could be causing this would be appreciated.
Can I get hold of a BIOS upgrade CD ISO that does not check the battery and charger state? I promise I won't let the machine die while the bios upgrade goes ahead!
Thanks in advance.Hi Ferdi
Thanks for your reply. I'll contact my supplier to get the chips I have exchanged. Not sure which numbers are my part's number. I have this:
Kingston Technology
KVR16LS11/4
4GB PC3L - 12800 CL11 204 SODIMM
KTC TA01536 9U5469-045.A00LF R3161
My laptop is Toshiba Satellite L655 - 146
The fact that the BIOS upgrade does not work still bugs me, though. At least I have a new battery now.
Thanks again. -
Sleeping firewire drive causes system crash
I have a 320 GB external firewire seagate drive connected to my Dual Ghz Quicksilver G4. At least twice a day, when I try to access that drive, I experience a system crash, what I believe to be a kernal panic. I get a message telling me I need to shut my computer down and restart it. I am thinking this is not so good for my computer.
So, either the hard drive is the problem or it's the third party firewire card i have installed in one of my PCI slots. But here's the thing, other drives are connected to that card.
Would keeping the Seagate drive awake stop this from happening? It goes to sleep all the time. Have others experienced problems with the seagate drives? Should I stop using it?Hi, Aaron. Welcome to the Discussions.
If you are seeing this message, that indicates a kernel panic.
There could be a problem with the FireWire drive or the card. If disconnecting the drive for a few days results in no additional panics, then it is the drive. For that, I'd contact Seagate. If not, the card becomes suspect. An examination of the panic log might prove helpful.
You can also try running Step 1 of the process specified in my "Resolving Disk, Permission, and Cache Corruption" FAQ against the Seagate FireWire drive.
Checking the FireWire cables, trying different cables or ports, checking that the card is installed correctly, checking that you assembled the Seagate drive and enclosure correctly (sounds like you built the FW drive) are some other troubleshooting steps to consider. The FireWire enclosure itself may be defective.
See also my "Resolving Kernel Panics" FAQ. This FAQ includes step-by-step instructions for identifying and resolving some of the most common causes of kernel panics, including tips like those above.
My FAQ is a roadmap: start at the beginning and work through to the end, following the instruction in the order specified, including the "If all else fails..." section if a cause or resolution is not found in an earlier troubleshooting step therein.
You maybe unable to prevent the FireWire drive from sleeping. Secondary hard drives (second internal, as well as external drives) may not respect the "Put the hard drive(s) to sleep when possible" option if de-selected. I discuss this particular issue in my "Spinning Beach Ball Of Death (SBBOD)" FAQ, specifically in the section entitled "SBBOD spins for 30-35 seconds. You may hear your hard drives spinning up."
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link. -
Pages 5.0 causes system crash?
Doe anybody experience system crashes with pages 5.0? I havent had a system crash since 2011 where my old MBP has a broken hard drive and a broken RAM.
Now I have A Retina MBP and it has been working great but I just had the first system crash and reboot while I was exporting a 70mb large PDF file from pages 5.0. Is this a Pages bug, or could my hardware be damaged?Thanks I already changed back after 1 day of using pages 5.0. But I had that one file left that I wanted to print quickly.
Anyway the issue is that I am not sure weather pages or my system caused the system crash. -
Ultiroute 2001 causes system crash at HASP install
I have an old version of Ultiroute which I only used occasionally on my older Dell D620 laptop. When I got my new (to me!) E6400 laptop, I installed Ultiboard 2001, but not Ultiroute. Now, whenever I try to install Ultiroute, the installer reaches the point where it is installing the HASP driver for the dongle, and every time it reaches this point, the system crashes hard - i.e. screen goes blank for 10 seconds, then the laptop reboots itself. After reboot, Windows tells me that it has receovered from a serious error. When I tell it to send a report, I get a web page that says the crash was caused by a device driver error.
Just for fun, I went to the Alladin website & tried their HASP driver - same result. Examining the parallel port driver in hardware manager (I use this laptop docked tro a Dell dock for Parallel port access) and telling it to look for an update, it says that no newer driver is available. At this point, I'm stuck. Anyone have any ideas? System is a Dell E6400, Win XP SP3. The software is Ultiroute 5.64. I know it's old, but it has worked acceptably in the past, and I have no budget for new software right now.Hi NevadaDave,
Ultiroute used the Alladin dongle for security protection and if the Alladin driver is crashing the computer, to be honest there is not much we can do about it anymore. From the Allinddin support page, there are several drivers; I am not sure which is the best one for the dongle that was shipped with Ultiroute so try a few.
http://www.aladdin.com/support/hasp/hasp4/enduser.asp
If none of the driver you tried worked, I believe the Personal Ultiroute version didn't require a dongle and I can get this for you. It will have fewer features than the version you own. If this is something you want, send me a private message with your Ultiboard serial number.
Tien P.
National Instruments
Maybe you are looking for
-
How can you remove clustering between two BO XI 3.1 Servers
Hi, Servers A and B have been clustered before and because we have done so many changes to each of the servers, we thought of uninstalling everything from both servers and reinstall BO XI 3.1 server on each. Installed BO XI 3.1 server on Server A, ap
-
I'm running a trial of Final Cut Pro X, but it doesn't recognize my Canon GL2. Any advice?
-
Please help!
-
Hello all, In SAP B1 2005B I am having 2 queries about Print Layout of PO. 1. In print layout of the Purchase Order .I want have the total of different taxes individually applied in the document. E.g. In PO having some rows with VAT@4% ,[email protec
-
It does NOT have a red light. I have had that issue before ad was able to fix it. My external output does NOT show up in my system preferences at all.