15-07-2020, 08:11 AM
(14-07-2020, 11:26 PM)mr-matt Wrote: Crashed again this morning. I found the full crash log this time: https://www.dropbox.com/sh/g91r6qfs0s4j0...D66ia?dl=0
It seems to be to do with Nvidia but it only occurs in the scene with an Obi Rope in it. The crash occurs as I'm loading the scene in (at runtime), but only on some occasions.
Some other details:
- Unity 2019.3.0f6
- .NET Standard 2.0
- My specs: https://www.dropbox.com/s/tuqptjvuekualx...g.txt?dl=0
Update: Another crash this morning https://www.dropbox.com/sh/cq3at3wnh637u...QBtEa?dl=0
Some digging around revealed that other people with the same "Unity.exe caused an access violation" type crashes had issues with third party plugins/native dlls. I'm fairly confident that the issue is to do with Obi as this crash never occurs when Obi is not in the scene.
Update 2: I'm also getting strange freezes where the editor becomes frozen while loading the scene, but the audio continues playing.
No crash log was produced but here is the editor log at the point of the freeze with full stack traces: https://www.dropbox.com/s/c8vfntk37yv9xu...5.log?dl=0
Could be that Obi is doing something that the gfx driver is not liking, but chances are it's something fairly standard. We are not doing anything out of the ordinary as far as graphics go. Access violations can be caused by any code that is currently running, be it a third party plugin, Unity, drivers...
Does this happen in a particular scene? If so, can you describe the contents/setup of it? It would also be useful to get our hands on a scene/project that reproduces this.