You are not logged in.

Announcement

[2017.09.08] DeployStudio build v1.7.8 (checksum, release note).
[2016.08.26] DeployStudio build v1.6.19 (release note).
[2013.02.23] DeployStudio last universal build v1.5.17 (release note).

#1 2019-01-30 17:16:33

boli
Member
From: Switzerland
Registered: 2016-12-22

DS Runtime 1.7.8 spinning beachball with new 15" MacBook Pros

Setup:
- Brand new 15" MacBook Pro, macOS 10.14.1 preinstalled (regular build 18B75).
- Installed DS Runtime 1.7.8 on it, to run our usual workflows for installation
- Our DS Server is selectable in the server selection popup
- When selecting it, or doing any other action in the DS Runtime, the spinning beachball appears and DS Runtime becomes unusable, and requires a Force Quit.

Instead of selecting our server, I can also open the DS Runtime Log, which also causes the spinning beachball to appear. But hey, at least it contains this info:

    2019-01-30 15:22:15.575 DeployStudio Runtime.bin[1294:20276] pid(1294)/euid(0) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
    2019-01-30 15:22:15.575 DeployStudio Runtime.bin[1294:20276] *** Assertion failure in void assertRunningOnAppKitThread(void)(), /BuildRoot/Library/Caches/com.apple.xbs/Sources/ViewBridge/ViewBridge-401.1/ViewBridgeUtilities.m:912

The second to last line appears several (8) times total, I omitted those here for clarity.

My colleague tells me that until about 2 weeks ago this could be worked around by installing all macOS updates before running DS Runtime, but now this procedure doesn't help.

So I suspect that back then he updated to 10.14.2, and now the update would be to 10.14.3. I could reproduce this issue on yet another 15" MBP with stock 10.14.1, and am trying the update it to 10.14.3 (as that's what our NetSUS returns). If the issue persists I'll try to update to 10.14.2 manually and see what happens. Or a fresh macOS 10.14.3 install from our NetSUS. Edit: err right, from a regular installer, because T2 Macs can't NetBoot. ><

In the mean time, maybe the hive mind here has some ideas. :)

P.S. in the system.log I find this:

    Jan 30 15:22:14 kruder DeployStudio Runtime.bin[1294]: DEPRECATED USE in libdispatch client: dispatch source activated with no event handler set; set a breakpoint on _dispatch_bug_deprecated to debug

Last edited by boli (2019-01-30 17:40:50)

Offline

#2 2019-01-30 17:51:03

boli
Member
From: Switzerland
Registered: 2016-12-22

Re: DS Runtime 1.7.8 spinning beachball with new 15" MacBook Pros

OK, so it didn't work after update the pre-installed OS to 10.14.3, nor did it work with a fresh 10.14.3 install – in both cases ultimately the same thing happens: spinning beachball, same entries in DSR Log and system.log.

On the fresh macOS install DSR crashed on the first launch, and on the second and later launches behaved as described above.

Last edited by boli (2019-01-30 17:52:44)

Offline

#3 2019-02-04 15:27:35

boli
Member
From: Switzerland
Registered: 2016-12-22

Re: DS Runtime 1.7.8 spinning beachball with new 15" MacBook Pros

This problem does not occur with a preinstalled macOS v10.13.6.

BTW in the Mojave tests I did grant full disk access to DeployStudio Runtime, because it can't do some of its work otherwise (specifically, it can't comment out the line starting with /home in the file /etc/auto_master, which we need to do in our setup, as we mount an NFS share into /home)

Last edited by boli (2019-02-04 15:28:13)

Offline

#4 2019-02-04 16:08:16

boli
Member
From: Switzerland
Registered: 2016-12-22

Re: DS Runtime 1.7.8 spinning beachball with new 15" MacBook Pros

This issue also does *not* happen on a Mac Pro (2013) with Mojave, nor on a Mac Mini (2018) with Mojave.

For some reason the problem also did not reoccur on a 15" MBP (2018) when running 10.14.1 *after* I ran our workflow (while booted off a 10.13.6 volume) with the 10.14.1 volume as installation target, then rebooted onto the 10.14.1 volume and ran DSR.

This was an accidental find while trying to find workarounds, an not reliable enough as a workaround.

Last edited by boli (2019-02-05 10:57:25)

Offline

#5 2019-02-05 10:55:14

boli
Member
From: Switzerland
Registered: 2016-12-22

Re: DS Runtime 1.7.8 spinning beachball with new 15" MacBook Pros

Fresh 10.14.1 install updated to 10.14.2 (I don't have a 10.14.2 direct installer handy) shows the same issue.

This time there was a stack trace in the DSR log, maybe this is helpful?

2019-02-05 10:48:29.076 DeployStudio Runtime.bin[1084:15966] pid(1084)/euid(0) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2019-02-05 10:48:29.078 DeployStudio Runtime.bin[1084:15966] WARNING: NSWindow drag regions should only be invalidated on the Main Thread! This will throw an exception in the future. Called from (
    0   AppKit                              0x00007fff28314ccc -[NSWindow(NSWindow_Theme) _postWindowNeedsToResetDragMarginsUnlessPostingDisabled] + 386
    1   AppKit                              0x00007fff2830e5d7 -[NSView removeFromSuperview] + 379
    2   AppKit                              0x00007fff28588f2d -[_NSKeyboardFocusClipView removeFromSuperview] + 55
    3   AppKit                              0x00007fff28519062 -[NSWindow endEditingFor:] + 429
    4   AppKit                              0x00007fff2830e4b7 -[NSView removeFromSuperview] + 91
    5   AppKit                              0x00007fff28588f2d -[_NSKeyboardFocusClipView removeFromSuperview] + 55
    6   AppKit                              0x00007fff28588bf2 -[NSCell endEditing:] + 677
    7   AppKit                              0x00007fff2882a637 -[NSComboBoxCell endEditing:] + 86
    8   AppKit                              0x00007fff285883d1 -[NSTextField textDidEndEditing:] + 367
    9   CoreFoundation                      0x00007fff2ada6712 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
    10  CoreFoundation                      0x00007fff2ada668c ___CFXRegistrationPost_block_invoke + 63
    11  CoreFoundation                      0x00007fff2ada65ad _CFXRegistrationPost + 398
    12  CoreFoundation                      0x00007fff2adaea09 ___CFXNotificationPost_block_invoke + 87
    13  CoreFoundation                      0x00007fff2ad161aa -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1633
    14  CoreFoundation                      0x00007fff2ad1556d _CFXNotificationPost + 742
    15  Foundation                          0x00007fff2d09da7b -[NSNotificationCenter postNotificationName:object:userInfo:] + 66
    16  AppKit                              0x00007fff28587e3c -[NSTextView(NSSharing) resignFirstResponder] + 870
    17  AppKit                              0x00007fff283e5522 -[NSWindow _realMakeFirstResponder:] + 258
    18  DeployStudio Runtime.bin            0x000000010103f7f4 -[MainController ZeroConfBrowseNewConnection:] + 3780
    19  CoreFoundation                      0x00007fff2ada6712 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
    20  CoreFoundation                      0x00007fff2ada668c ___CFXRegistrationPost_block_invoke + 63
    21  CoreFoundation                      0x00007fff2ada65ad _CFXRegistrationPost + 398
    22  CoreFoundation                      0x00007fff2adaea09 ___CFXNotificationPost_block_invoke + 87
    23  CoreFoundation                      0x00007fff2ad161aa -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1633
    24  CoreFoundation                      0x00007fff2ad1556d _CFXNotificationPost + 742
    25  Foundation                          0x00007fff2d09da7b -[NSNotificationCenter postNotificationName:object:userInfo:] + 66
    26  DSZeroConf                          0x000000010115464e -[DSZeroConfBrowse updateConnectionThreaded:] + 1502
    27  DSZeroConf                          0x00000001011547e2 __48-[DSZeroConfBrowse netServiceDidResolveAddress:]_block_invoke + 50
    28  libdispatch.dylib                   0x00007fff57f30d53 _dispatch_call_block_and_release + 12
    29  libdispatch.dylib                   0x00007fff57f31dcf _dispatch_client_callout + 8
    30  libdispatch.dylib                   0x00007fff57f34240 _dispatch_queue_override_invoke + 767
    31  libdispatch.dylib                   0x00007fff57f3fd26 _dispatch_root_queue_drain + 325
    32  libdispatch.dylib                   0x00007fff57f404bd _dispatch_worker_thread2 + 90
    33  libsystem_pthread.dylib             0x00007fff581726dd _pthread_wqthread + 619
    34  libsystem_pthread.dylib             0x00007fff58172405 start_wqthread + 13
)
2019-02-05 10:48:29.078 DeployStudio Runtime.bin[1084:15966] pid(1084)/euid(0) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!

Offline

#6 2019-02-05 13:50:59

boli
Member
From: Switzerland
Registered: 2016-12-22

Re: DS Runtime 1.7.8 spinning beachball with new 15" MacBook Pros

Tried a fresh 10.14.3 install on a MBP 13" (early 2015), DSR runs flawlessly. Only 15" MBP (2018) make trouble. The same TIS/TSM error messages appear in the DSR log on the 13".




The following "workaround" worked a second time on a MBP 15" (2018):
- A 10.14.1 fresh install, updated to 10.14.2 with combo updater
- Then booted to a 10.13.6 volume, to run our DSR workflow on the 10.14.2 volume.
- Booted off this 10.14.2 volume
- First launch of DSR: it hangs (spinning beachball), our server does not appear in popup
- Force quit and relaunch of DSR: our server appears selecte in popup automatically, could enter name *and* password (without spinning beachball) and run workflow

Offline

#7 2019-02-07 11:26:19

boli
Member
From: Switzerland
Registered: 2016-12-22

Re: DS Runtime 1.7.8 spinning beachball with new 15" MacBook Pros

My colleague found a very simple workaround by accident:

Don't have the ethernet adapter connected to the MacBook Pro when launching the DeployStudio Runtime. Then it won't freeze, and the server, user name and password can be entered without any trouble.

Once the ethernet adapter is connected, it will connect to the server without "beachballing" and everything works as usual after that.

Offline

#8 2019-02-07 11:28:51

boli
Member
From: Switzerland
Registered: 2016-12-22

Re: DS Runtime 1.7.8 spinning beachball with new 15" MacBook Pros

So it seems that the spinning beachball may be somehow related to server discovery, and this in turn makes me think of this:

Until recently, we used to have a second DS server in our network, because one of our employees installed the full DS server instead of just the DS runtime. Naturally I told him to uninstall the server once I discovered it, and that coincides roughly with the time that my colleague noticed the spinning beachball issues. So maybe the second server may have prevented this spinning beachball issue, because it may have changed the server discovery process in some way, like having the network disconnected does too (but differently).

Last edited by boli (2019-02-07 11:30:51)

Offline

Board footer

Powered by FluxBB