Xojo 2020 R2 locks up on quit

This is a continuation of a beta discussion here: https://forum.xojo.com/t/51267-locks-up-on-quit/58779

With the following steps, the Xojo IDE locks up:

<https://xojo.com/issue/62862>

  • Launch Xojo
  • Open a Web 2 project (text format, in case that matters)
  • Command-R to Debug Run
  • Command-. to terminate debug run
  • Command-K to analyze: wait until it completes
  • Command-Q to quit.

The app goes “not responding” and a sample using Activity monitor shows this:

Sampling process 12938 for 3 seconds with 1 millisecond of run time between samples
Sampling completed, processing symbols...
Analysis of sampling Xojo (pid 12938) every 1 millisecond
Process:         Xojo [12938]
Path:            /Applications/Xojo 2020 Release 2/Xojo 2020 R2.app/Contents/MacOS/Xojo
Load Address:    0x10208f000
Identifier:      com.xojo.xojo
Version:         20.2.0.51448 (20.2.0.3.51448)
Code Type:       X86-64
Parent Process:  ??? [1]

Date/Time:       2020-11-27 09:00:48.191 -0800
Launch Time:     2020-11-27 08:58:57.043 -0800
OS Version:      Mac OS X 10.14.6 (18G6042)
Report Version:  7
Analysis Tool:   /usr/bin/sample

Physical footprint:         1.1G
Physical footprint (peak):  1.4G
----

Call graph:
    2390 Thread_7675823   DispatchQueue_1: com.apple.main-thread  (serial)
    + 2390 start  (in libdyld.dylib) + 8  [0x7fff669fb3dc]
    +   2390 exit  (in libsystem_c.dylib) + 55  [0x7fff66aa16b3]
    +     2390 __cxa_finalize_ranges  (in libsystem_c.dylib) + 319  [0x7fff66aa13cf]
    +       2390 ???  (in XojoFramework)  load address 0x1135d8000 + 0xcd337  [0x1136a5337]
    +         2390 ???  (in XojoFramework)  load address 0x1135d8000 + 0xcd370  [0x1136a5370]
    +           2390 RuntimeUnlockObject  (in XojoFramework) + 523  [0x113846693]
    +             2390 0x0
    +               2390 _sigtramp  (in libsystem_platform.dylib) + 29  [0x7fff66be6b5d]
    +                 2390 ???  (in IDEUtils.dylib)  load address 0x114804000 + 0x37e7  [0x1148077e7]
    +                   2390 ???  (in IDEUtils.dylib)  load address 0x114804000 + 0x390c  [0x11480790c]
    2390 Thread_7675972: com.apple.NSEventThread
    + 2390 thread_start  (in libsystem_pthread.dylib) + 13  [0x7fff66bee40d]
    +   2390 _pthread_start  (in libsystem_pthread.dylib) + 66  [0x7fff66bf2249]
    +     2390 _pthread_body  (in libsystem_pthread.dylib) + 126  [0x7fff66bef2eb]
    +       2390 _NSEventThread  (in AppKit) + 175  [0x7fff380214a2]
    +         2390 CFRunLoopRunSpecific  (in CoreFoundation) + 455  [0x7fff3aa23552]
    +           2390 __CFRunLoopRun  (in CoreFoundation) + 1612  [0x7fff3aa23df0]
    +             2390 __CFRunLoopServiceMachPort  (in CoreFoundation) + 328  [0x7fff3aa24882]
    +               2390 mach_msg  (in libsystem_kernel.dylib) + 60  [0x7fff66b30768]
    +                 2390 mach_msg_trap  (in libsystem_kernel.dylib) + 10  [0x7fff66b3021a]
    2390 Thread_7681080
    + 2390 start_wqthread  (in libsystem_pthread.dylib) + 13  [0x7fff66bee3fd]
    +   2390 _pthread_wqthread  (in libsystem_pthread.dylib) + 458  [0x7fff66bee636]
    +     2390 __workq_kernreturn  (in libsystem_kernel.dylib) + 10  [0x7fff66b31bfa]
    627 Thread_7679052
      627 start_wqthread  (in libsystem_pthread.dylib) + 13  [0x7fff66bee3fd]
        627 _pthread_wqthread  (in libsystem_pthread.dylib) + 458  [0x7fff66bee636]
          627 __workq_kernreturn  (in libsystem_kernel.dylib) + 10  [0x7fff66b31bfa]

Total number in stack (recursive counted multiple, when >=5):

Sort by top of stack, same collapsed (when >= 5):
        __workq_kernreturn  (in libsystem_kernel.dylib)        3017
        ???  (in IDEUtils.dylib)  load address 0x114804000 + 0x390c  [0x11480790c]        2390
        mach_msg_trap  (in libsystem_kernel.dylib)        2390

Quits fine on BS.

1 Like

Can you try it with the web sample project shipped with R2: Example Projects / Web / Controls / WebFileUploader?

  • Launch Xojo
  • Open the sample project
  • Command-R to Debug Run (wait until it launches)
  • click back to select the IDE window debugger tab
  • Command-. to terminate debug run (wait until it terminates)
  • Command-K to analyze: wait until it completes
  • Command-Q to quit

For me, on 10.14.6, it’s 100% reproducible.

I had a similar issue until I restarted my Mini. Then it was OK.

I just restarted, and now I’m not seeing the bug.

*#%!^%!#$^$ Apple!