You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are working on a game in Unity and are using the deformer plugin in certain parts of the game. As soon as an action that uses the plugin is triggered, the game crashes with an "Unhandled exception : access violation writing location" error. This happens only in IL2CPP builds. Mono builds work perfectly fine without any crashes. When I debug the crash.dmp file, the detailed error message that I get is "Unhandled exception at 0x00007FFC38D71003 (GameAssembly.dll) in crash.dmp: 0xC0000005: Access violation writing location 0x0000000000000000. occurred". The crash occurs in the "ResetNormalsJob - Execute" method. I am attaching the crash.dmp file and error log as well as screenshots of the call stack and crash location below.
Hey so sorry for the delay - I hope you've been able to find a workaround!
From what I can tell, that seems like an issue with the IL2CPP compiler. I'm actually not sure if there's anything I can do on my end. There's a small chance the problem is with the burst compiler. To test, you could comment out the BurstCompile attribute on the ResetNormalsJob, but the job is so simple it suggests to me that the problem is external and warrants a bug report to Unity.
We are working on a game in Unity and are using the deformer plugin in certain parts of the game. As soon as an action that uses the plugin is triggered, the game crashes with an "Unhandled exception : access violation writing location" error. This happens only in IL2CPP builds. Mono builds work perfectly fine without any crashes. When I debug the crash.dmp file, the detailed error message that I get is "Unhandled exception at 0x00007FFC38D71003 (GameAssembly.dll) in crash.dmp: 0xC0000005: Access violation writing location 0x0000000000000000. occurred". The crash occurs in the "ResetNormalsJob - Execute" method. I am attaching the crash.dmp file and error log as well as screenshots of the call stack and crash location below.
CrashInfo.zip
The text was updated successfully, but these errors were encountered: