I noticed a strange behaviour, resulting in FG shutdown. The relevant entries in log seem to be:
3928.73 [ALRT]:nasal Nasal runtime error: non-objects have no members
3928.73 [ALRT]:nasal at /home/x/snap/flightgear/common/fgdata/Aircraft/c172p/Models/Interior/Panel/Instruments/garmin196/garmin196.nas, line 227
3928.73 [ALRT]:nasal called from: /home/x/snap/flightgear/common/fgdata/Aircraft/c172p/Models/Interior/Panel/Instruments/garmin196/garmin196.nas, line 3239
3928.73 [ALRT]:nasal called from: /home/x/snap/flightgear/common/fgdata/Aircraft/c172p/Models/Interior/Panel/Instruments/garmin196/garmin196.nas, line 323
then a couple of:
[ALRT]:nasal ERROR: Cannot add listener to tied property /controls[0]/lighting[0]/landing-lights[0]
and the last line:
AL lib: (EE) ALCpulsePlayback_streamStateCallback: Received stream failure!
FG version: 2020.3.8
command line: flightgear --launcher --httpd=8080 --enable-fgcom --enable-auto-coordination
OS: Ubuntu 16.04.7 LTS
Multiplayer enabled
It happened twice in similar circumstances, seems reproducible:
1. fly (I did EPGD->EPBY)
2. land and taxi to apron
3. shutdown aircraft, but leave FG running.
4. go for a sandwich or lunch (in other words, leave FG running for a while)
5. come back, access menu (for example press 'File') --> FG will crash
If it is known, apologies.
If more information is needed, let me know.
Mariusz (SP-MRM)