LLVM sometime crashes on Mono

on version Fire (i have problem with compilation (on latest i have the same problem but more often)
MacOS 10.15.7 Catalina
Project IOS with many shared lib.

Mono crash… Can I update something ? Can you give me some direction ?

Native Crash Reporting

Got a segv while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.

Native stacktrace:

    0x1079f40b4 - /Applications/Fire.app/Contents/Resources/Mono/bin/mono-sgen : dump_native_stacktrace
    0x1079f4011 - /Applications/Fire.app/Contents/Resources/Mono/bin/mono-sgen : mono_dump_native_crash_info
    0x1078decea - /Applications/Fire.app/Contents/Resources/Mono/bin/mono-sgen : mono_handle_native_crash
    0x1079dc0bf - /Applications/Fire.app/Contents/Resources/Mono/bin/mono-sgen : altstack_handle_and_restore
    0x126140074 - /Applications/Fire.app/Contents/Frameworks/libRemObjects.Elements.LLVM.dylib : _ZN4llvm16MetadataTracking7untrackEPvRNS_8MetadataE
    0x12523ce5e - /Applications/Fire.app/Contents/Frameworks/libRemObjects.Elements.LLVM.dylib : _ZN12_GLOBAL__N_126AArch64InstructionSelectorD0Ev
    0x1254063aa - /Applications/Fire.app/Contents/Frameworks/libRemObjects.Elements.LLVM.dylib : _ZN4llvm16AArch64SubtargetD2Ev
    0x12540824f - /Applications/Fire.app/Contents/Frameworks/libRemObjects.Elements.LLVM.dylib : _ZN4llvm20AArch64TargetMachineD2Ev
    0x125408b7e - /Applications/Fire.app/Contents/Frameworks/libRemObjects.Elements.LLVM.dylib : _ZN4llvm22AArch64leTargetMachineD0Ev
    0x118dbf493 - Unknown
    0x109e2fd51 - /Applications/Fire.app/Contents/Resources/Mono/lib/mono/4.5/mscorlib.dll.dylib : System_Threading_Tasks_Task_InnerInvoke
    0x109e2fcdc - /Applications/Fire.app/Contents/Resources/Mono/lib/mono/4.5/mscorlib.dll.dylib : System_Threading_Tasks_Task_ExecutionContextCallback_object
    0x109dfde53 - /Applications/Fire.app/Contents/Resources/Mono/lib/mono/4.5/mscorlib.dll.dylib : System_Threading_ExecutionContext_Run_System_Threading_ExecutionContext_System_Threading_ContextCallback_object_bool
    0x109e2fc1d - /Applications/Fire.app/Contents/Resources/Mono/lib/mono/4.5/mscorlib.dll.dylib : System_Threading_Tasks_Task_ExecuteEntry_bool
    0x109e064ed - /Applications/Fire.app/Contents/Resources/Mono/lib/mono/4.5/mscorlib.dll.dylib : System_Threading__ThreadPoolWaitCallback_PerformWaitCallback
    0x1077d7525 - /Applications/Fire.app/Contents/Resources/Mono/bin/mono-sgen : mono_jit_runtime_invoke
    0x107ba7c8a - /Applications/Fire.app/Contents/Resources/Mono/bin/mono-sgen : do_runtime_invoke
    0x107ba15c0 - /Applications/Fire.app/Contents/Resources/Mono/bin/mono-sgen : mono_runtime_try_invoke
    0x107beaec9 - /Applications/Fire.app/Contents/Resources/Mono/bin/mono-sgen : try_invoke_perform_wait_callback
    0x107bea53e - /Applications/Fire.app/Contents/Resources/Mono/bin/mono-sgen : worker_callback
    0x107a93497 - /Applications/Fire.app/Contents/Resources/Mono/bin/mono-sgen : worker_thread
    0x107be5061 - /Applications/Fire.app/Contents/Resources/Mono/bin/mono-sgen : start_wrapper_internal
    0x107be4c84 - /Applications/Fire.app/Contents/Resources/Mono/bin/mono-sgen : start_wrapper
    0x7fff6d43a109 - /usr/lib/system/libsystem_pthread.dylib : _pthread_start
    0x7fff6d435b8b - /usr/lib/system/libsystem_pthread.dylib : thread_start

Telemetry Dumper:

Pkilling 0x123145567526912x from 0x123145580183552x
Pkilling 0x123145586511872x from 0x123145580183552x
Pkilling 0x123145565417472x from 0x123145580183552x
Pkilling 0x123145584402432x from 0x123145580183552x
Pkilling 0x123145563308032x from 0x123145580183552x
Pkilling 0x123145582292992x from 0x123145580183552x
Pkilling 0x123145561198592x from 0x123145580183552x
Pkilling 0x4532559296x from 0x123145580183552x
Pkilling 0x123145559089152x from 0x123145580183552x
Pkilling 0x123145555906560x from 0x123145580183552x
Could not exec mono-hang-watchdog, expected on path ‘/Applications/Fire.app/Contents/Resources/Mono/lib/…/etc/…/bin/mono-hang-watchdog’ (errno 2)
Pkilling 0x123145578074112x from 0x123145580183552x
Pkilling 0x123145575964672x from 0x123145580183552x
Pkilling 0x123145573855232x from 0x123145580183552x
Pkilling 0x123145592840192x from 0x123145580183552x
Pkilling 0x123145571745792x from 0x123145580183552x
Pkilling 0x123145569636352x from 0x123145580183552x
Pkilling 0x123145588621312x from 0x123145580183552x
Entering thread summarizer pause from 0x123145580183552x
Finished thread summarizer pause from 0x123145580183552x.
Failed to create breadcrumb file (null)/crash_hash_0x122409a9ce

Waiting for dumping threads to resume

External Debugger Dump:

Basic Fault Address Reporting

Memory around native instruction pointer (0x126140074):0x126140064 eb ca 4d 85 c9 49 0f 45 d1 eb 89 90 55 48 89 e5 …M…I.E…UH…
0x126140074 8a 0e 8d 41 fc 3c 1e 76 17 8d 51 ff 31 c0 80 fa …A.<.v…Q.1…
0x126140084 02 48 0f 42 c6 48 85 c0 74 71 48 83 c0 08 eb 1d .H.B.H…tqH…
0x126140094 8a 46 01 24 7f 3c 02 74 06 83 7e 0c 00 74 69 48 .F.$.<.t…~…tiH

Managed Stacktrace:

      at <unknown> <0xffffffff>
      at LLVM.Interop.LLVMInterop:LLVMDisposeTargetMachine <0x000a2>
      at <>c__DisplayClass13:<a>b__0 <0x034aa>
      at System.Threading.Tasks.Task:InnerInvoke <0x00060>
      at System.Threading.Tasks.Task:Execute <0x00037>
      at System.Threading.Tasks.Task:ExecutionContextCallback <0x0005b>
      at System.Threading.ExecutionContext:RunInternal <0x00191>
      at System.Threading.ExecutionContext:Run <0x00042>
      at System.Threading.Tasks.Task:ExecuteWithThreadLocal <0x000f6>
      at System.Threading.Tasks.Task:ExecuteEntry <0x000dc>
      at System.Threading.Tasks.Task:System.Threading.IThreadPoolWorkItem.ExecuteWorkItem <0x00026>
      at System.Threading.ThreadPoolWorkQueue:Dispatch <0x00279>
      at System.Threading._ThreadPoolWaitCallback:PerformWaitCallback <0x0001c>
      at <Module>:runtime_invoke_bool <0x000a5>


Best regards

We’re already looking into this, @JohnMoshakis reported this the other day and I see it too. The crash is intermittent, and simply building again usually/always fixes the issue (for me, at least).

Does it really happen more often with latest, or could that be subjective?

In my project more often I think (I came back to 2657).
I have one more problem after compilation when error appears clicking on it I can’t go to file and line with this error (nothing happens)

Strange. We’ll know more once we figure out what causes this, I guess. At this stage, im not sure of its a Mono bug our ours.

Do you sue the embedded compiler & mono, or an external compiler and mono install? in the latter case, whats your version of Mono?

Are you on an Arm or Intel Mac?

Are you on an Arm or Intel Mac?

Do you sue the embedded compiler & mono, or an external compiler and mono install? in the latter case, whats your version of Mono?

Internal Mono 6.13.0

Do you need any other info ?

No, thats all, thanx. so its not CPU specific (im on Arm), and it shows out internal Mono and the current shipped Mono installer (which im using with the external compiler)

Marc what can I do with it ?
I have one more problem after compilation when error appears clicking on it I can’t go to file and line with this error (nothing happens)

Right now, nothing but be sad you wasted some time waiting for the project to build, and hit build (or run) again, the second build should succeed.

At least it does for me. I see this crash once or twice a day, but never twice in a row…