Comment 94 for bug 1861936

@juergh I may have (somewhat) found the trigger.

As previously noted, my internal clients have a static route to the remote wireguard networks via my raspberry pi. This is defined in my internal router (Unifi)
ie:
client > router > static route (10.241.0.0/24) to pi eth0 IP > pi > tunnel > VPS

If have disabled this route, so now none of my clients can send data over the tunnel. Only the Pi which is running the tunnel itself is able to communicate over said tunnel.
No crashes at all.

So, with this in mind, setup an internal client with a static route to your wireguard network and start sending traffic to the remote site. This should (hopefully) trigger the issue.