Steven Sokol

Here's what that outputs: ``` # To display the perf.data header info, please use --header/--header-only options. # # comm: fvUnisocket # # Total Lost Samples: 0 # # Samples: 80K...

Not a problem. Just want to get to the bottom of this if possible. 1. Here you go: ``` root@pi4cm1(rw):/# perf report --stdio --dso fvUnisocket Warning: 1 map information files...

I rebuilt with "GOARM=7" and that seems to have resolved the issue. I've run the rebuilt version for the past week without a lockup / runaway. The only problem is,...

``` root@pi4cm1(rw):~# uname -a Linux pi4cm1 5.10.63-v7l+ #1457 SMP Tue Sep 28 11:26:14 BST 2021 armv7l GNU/Linux ```

Looks like thread safety is a feature of v5 and later, so I'll try moving to that.

I'm running the latest / greatest (geos (5.0.0), GEOSwift (7.1.0)) and still seeing data race issues like: ``` ================== WARNING: ThreadSanitizer: data race (pid=93529) Write of size 1 at 0x000108d04a00...

Ah, that's the one I should have updated. Apologies for that.

Thank you. Just to double check: does the second warning about simultaneous writes to addRef() also have no practical impact on the application? I'm happy to ignore these if that's...

Thanks! Please let me know if anyone needs additional information from me.

At this point, if I understand the code in traffic.go, we're excluding all traffic messages that match the ICAO code entered for "OwnshipModeS". Those messages get assigned to a variable...