Spinning Pizza of Death when selecting Run

I’m developing an iOS app using the latest version of Xojo on an M1 mini running MacOS 12.2.1.

Mostly it’s nice and snappy, but about 1 time in 10 when I select the Run button I get a SPoD and Xojo goes completely unresponsive for several minutes. Then suddenly I get the compiling pop-up window and shortly later the app launches in the Simulator as usual.

Running Activity Monitor does not show any CPU or other resource usage when this occurs.

Appreciate any thoughts you might have.

code signing

Sophos antivirus or equivalent causing a long delay?

When you press run or CMD+R release the buttons asap, if you hold it for too long it may cause a delay. i think greg once said that an since forever i’ve not had delays after that.

Nope, no AV installed. And no CPU activity by any process.

Still having this problem, except that now the SPOD occurs when editing code. It could be a text selection, copy, duplicate, etc. The hang lasts about 10 minutes, then everything is fine. Only Xojo exhibits this behavior. Activity Monitor doesn’t show anything spiking anywhere. The Xojo preference file looks uncorrupted. I would blame my buggy M1 mini, which requires an occasional Bluetooth reset, except that it happens only with Xojo.

I’d check some things:
1: with disk utility, check your hard disk (including external ones). A file system going corrupted may produce the symptoms you’re seeing (because Xojo would wait on resources that take time to come).
2: are you using network drive? Sometimes, a busy server (or a poor connection) can delay the asked resource to come, leading to an app hanging.
3: is your RAM possibly full? How much does Xojo take?

The fact it only happens with Xojo doesn’t surprise me. While I can’t explain much (barely a feeling of Xojo using old API or being complex), I’ve seen behaviours like that which only Xojo has among the apps I use.

does Xojo write a log (with timestamps) after click on Run?
could be a integrated webservice that do the delay?

Where is located the XCode application ?
In a remote server ?

Is XCode always running when you run your iOS project ?

Where is located the XCode application ?
In a remote server ?

Is XCode always running when you run your iOS project ?

On the local drive. It’s normally not running.

No web service.

Memory pressure is low. Xojo doesn’t take an inordinate amount compared to other apps running.

No. Only a NAS Volume only mounted during Time Machine backups.

Disk Utility found no problems with my internal drive, my external CCC Backup drive, or my external Time Machine drive.

And, the obvious: have you tried sampling Xojo from the Activity monitor? You can post it here.

Good suggestion. I’ll do this the next time the hang occurs.

Xojo hung while attempting to duplicate a method in the IDE. What’s a mach_message_trap?

  2544 Thread_106103: com.apple.NSURLConnectionLoader
    + 2544 thread_start  (in libsystem_pthread.dylib) + 8  [0x195d0be2c]
    +   2544 _pthread_start  (in libsystem_pthread.dylib) + 148  [0x195d1106c]
    +     2544 __NSThread__start__  (in Foundation) + 716  [0x196cf1470]
    +       2544 ???  (in CFNetwork)  load address 0x19a595000 + 0x253500  [0x19a7e8500]
    +         2544 CFRunLoopRunSpecific  (in CoreFoundation) + 612  [0x195dee888]
    +           2544 __CFRunLoopRun  (in CoreFoundation) + 1232  [0x195def4ac]
    +             2544 __CFRunLoopServiceMachPort  (in CoreFoundation) + 160  [0x195df0bc0]
    +               2544 mach_msg  (in libsystem_kernel.dylib) + 24  [0x195cd20ec]
    +                 2544 mach_msg_overwrite  (in libsystem_kernel.dylib) + 540  [0x195cda5c4]
    +                   2544 mach_msg2_internal  (in libsystem_kernel.dylib) + 80  [0x195ce38a4]
    +                     2544 mach_msg2_trap  (in libsystem_kernel.dylib) + 8  [0x195cd1d70]
    2544 Thread_5197881
      2544 start_wqthread  (in libsystem_pthread.dylib) + 8  [0x195d0be20]
        2544 _pthread_wqthread  (in libsystem_pthread.dylib) + 364  [0x195d0d14c]
          2544 __workq_kernreturn  (in libsystem_kernel.dylib) + 8  [0x195cd3a1c]

Total number in stack (recursive counted multiple, when >=5):
        5       mach_msg2_internal  (in libsystem_kernel.dylib) + 80  [0x195ce38a4]
        5       mach_msg2_trap  (in libsystem_kernel.dylib) + 0  [0x195cd1d68]

It’s a long story, but I was running with display Zoom all the time. Just bought a new monitor and no longer using Zoom and the problem has vanished.

1 Like