Debugging Unity standalone player immediately terminates with exit code 1
Hello,
I need to debug my game build. I use the standalone player build & debug config and put my game's executable, leaving the rest at default. When I click Debug, Rider initiates the debugger and launches the executable but the executable just spits out the [UnityMemory] configuration parameters and then immediately generates
Process '…./Builds/Linux/linux.x86_64' was terminated with exit code 1
At that point, the debugger is not even done initializing. This is on Manjaro Linux, Rider 2024.2.7, Unity 2021.3.39f1 with IL2CPP Linux build support. “Development build” was activated.
The executable works when started from the file browser or a terminal.
I retried with an almost empty Unity project (built-in render pipeline, added an empty game object with an empty script and created a development build) and it has the same issue.
I don't even know where to start investigating, so any help is appreciated.
Please sign in to leave a comment.
Hello,
Could you please share Rider logs collected with some extended diagnostics:
Upload the archive it to our server and share the ID.
Hello,
thanks for your reply. I uploaded the requested file and got the ID 2024_10_30_EDXaDg7McR48Zo3iCmN8uS.
I meanwhile accidentally figured out that the error does not occur when I use a non-development build. Rider will successfully start the build in that case. Of course a build without debug symbols is not very useful for debugging but maybe it helps find the issue.
Thanks you for the logs. I have submitted a new bug report: RIDER-119808 Standalone player debugging in Unity ends immediately. Please upvote the issue and keep an eye on further updates from the development team.