Passing on this crash report from 2020.2 from Julien:
Memory allocation error:
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information:
abort() called
fgfs(14603,0x112351dc0) malloc: *** error for object 0x404040404040404: pointer being freed was not allocated
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff6a7ac33a __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff6a868e60 pthread_kill + 430
2 libsystem_c.dylib 0x00007fff6a733808 abort + 120
3 libsystem_malloc.dylib 0x00007fff6a82950b malloc_vreport + 548
4 libsystem_malloc.dylib 0x00007fff6a82c40f malloc_report + 151
5 org.flightgear.mac-nightly 0x000000010c19334c 0x10b912000 + 8917836
6 org.flightgear.mac-nightly 0x000000010c1431d1 dns_ioevent + 1873
7 org.flightgear.mac-nightly 0x000000010c22ebce SGSubsystemGroup::Member::update(double) + 110
8 org.flightgear.mac-nightly 0x000000010c22e11d SGSubsystemGroup::update(double) + 781
9 org.flightgear.mac-nightly 0x000000010c233594 SGSubsystemMgr::update(double) + 52
10 org.flightgear.mac-nightly 0x000000010bf978f3 0x10b912000 + 6838515
11 org.flightgear.mac-nightly 0x000000010bf10afa fgOSMainLoop() + 186
Further detailed crash report attatched
Crashed in dns_assert_ctx in the uDNS code. Very weird.
Was it a one-off or reproducible?
This was a one-off, and just happened "randomly" during a flight.
There seems to be a possibility the multiplayer dialog is a trigger for this one -- a couple of reports from both windows and mac. Haven't seen it myself.