I’m currently getting a crash with AOnlineBeaconClient when NetDriver is not valid.
- I host a listen server
- I launch a client that then pings the listen server.
- If I close the listen server sometime after, the client crashes.
- The debug has an exception thrown at line 306 of OnlineBeaconClient.cpp
This does not happen if I close a dedicated server which leads me to believe that things are handled differently with them.
Is there anything specific I should do when shutting down a listen server to prevent it from crashing all servers that connected (but called DestroyBeacon())?
It seems when I close the listen server, the client has AOnlineBeaconClient::OnFailure() called before AOnlineBeaconClient::NotifyControlMessage is called.
This leads to NetDriver being set to null. Because NotifyControlMessage does not validate the pointer, it results in a hard crash.
I still need to figure out why a listen server causes this to happen.
We’ve recently made a switch to a new bug reporting method using a more structured form. Please visit the link below for more details and report the issue using the new Bug Submission Form. Feel free to continue to use this thread for community discussion around the issue.