DADman SWOD on quit

[LukeHoward]

DADman really likes to SWOD when quitting (at the end of the day, when I shut down). Have to force quit. Anyone else seen this?

I'm on 5.5.0.2. I can't attach a debugger, but looking at a sample taken from Activity Monitor it appears that pthread_join() in the main thread is deadlocked.

Heaviest stack for the main thread of the target process:
  10  start + 1 (libdyld.dylib + 109769) [0x7fff70dfecc9]
  10  NSApplicationMain + 777 (AppKit + 14758) [0x7fff33e379a6]
  10  -[NSApplication run] + 707 (AppKit + 203759) [0x7fff33e65bef]
  10  -[NSApplication(NSEvent) sendEvent:] + 1161 (AppKit + 1985997) [0x7fff34018dcd]
  10  routeKeyEquivalent + 521 (AppKit + 8160587) [0x7fff345fc54b]
  10  -[NSMenu performKeyEquivalent:] + 412 (AppKit + 3744775) [0x7fff341c6407]
  10  -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 106 (AppKit + 3749130) [0x7fff341c750a]
  10  -[NSMenuItem _corePerformAction] + 312 (AppKit + 3749774) [0x7fff341c778e]
  10  -[NSApplication(NSResponder) sendAction:to:from:] + 299 (AppKit + 2637047) [0x7fff340b7cf7]
  10  -[NSApplication terminate:] + 1385 (AppKit + 3205160) [0x7fff34142828]
  10  -[NSNotificationCenter postNotificationName:object:userInfo:] + 59 (Foundation + 36998) [0x7fff39247086]
  10  _CFXNotificationPost + 1351 (CoreFoundation + 299577) [0x7fff36bc7239]
  10  -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1554 (CoreFoundation + 302477) [0x7fff36bc7d8d]
  10  ___CFXNotificationPost_block_invoke + 80 (CoreFoundation + 498724) [0x7fff36bf7c24]
  10  _CFXRegistrationPost1 + 372 (CoreFoundation + 499640) [0x7fff36bf7fb8]
  10  ___CFXRegistrationPost1_block_invoke + 63 (CoreFoundation + 499779) [0x7fff36bf8043]
  10  __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12 (CoreFoundation + 499887) [0x7fff36bf80af]
  10  ??? (DADman + 574067) [0x1014be273]
  10  ??? (DADman + 572600) [0x1014bdcb8]
  10  ??? (DADman + 210116) [0x1014654c4]
  10  ??? (DADman + 207348) [0x1014649f4]
  10  ??? (DADman + 209781) [0x101465375]
  10  ??? (DADman + 721472) [0x1014e2240]
  10  ??? (DADman + 18707) [0x101436913]
  10  ??? (DADman + 23683) [0x101437c83]
  10  __ulock_wait + 10 (libsystem_kernel.dylib + 9566) [0x7fff70f4155e]
 *10  ??? (kernel + 6976240) [0xffffff80008a72f0]

[Jeff Schmidt]

Yes. Nearly daily. Occasionally it will quit without hanging, but that's the exception.

[gives]

Yes, Me too. What has fixed it for me is to wait a bit after PT quits like a couple of minutes and then quit DADMAN. I have not had it happen in a while either way though. You have set up a separate IP address for the MTRX right? That is part of the deal to make things happy.
G

[BScout]

I don't have this issue.
What operating system are you on, Luke? I'm still on High Sierra.

[LukeHoward]

Originally Posted by BScout

I don't have this issue.
What operating system are you on, Luke? I'm still on High Sierra.

I’m on 10.15.7.

[BScout]

Gregory is too.
If Jeff is also, that may be the common issue.

Also, is everyone having this problem on Mac Pro 6,1 (black trashcans?)

I have to check but I have a Mac Pro 7,1 (new Cheesegrater) that I believe is on 10.15.7 that doesn't lock up. But with that one, it is communicating over a third-party USB to Gigabit ethernet (due to the 10GbE NIC not working with Dante) and a MTRX Studio is on the other end instead of a MTRX.

[LukeHoward]

Originally Posted by BScout

Gregory is too.
If Jeff is also, that may be the common issue.

Also, is everyone having this problem on Mac Pro 6,1 (black trashcans?)

I have to check but I have a Mac Pro 7,1 (new Cheesegrater) that I believe is on 10.15.7 that doesn't lock up. But with that one, it is communicating over a third-party USB to Gigabit ethernet (due to the 10GbE NIC not working with Dante) and a MTRX Studio is on the other end instead of a MTRX.

I’m using the built in NIC on a 7,1. Using EuCon too, perhaps there’s an order of shutdown issue.