Forum Discussion

🚨 This forum is archived and read-only. To submit a forum post, please visit our new Developer Forum. 🚨
shinymark's avatar
shinymark
Honored Guest
12 years ago

Unity editor crash with 0.4.3

I'm getting a crash in the Unity editor when entering play mode. It's 100% reproducible in my project. It appears to originate in OculusPlugin.dll. As you can imagine, this makes testing pretty frustrating.

Steps:

1. Open project
2. Enter play mode in the editor, the game runs successfully with typical Oculus distorted 2 camera setup in game view
3. Exit play mode
4. Enter play mode again
5. 100% crash, nothing displayed in game view before the crash

OS: Windows 8.1
Unity: 4.5.5 Pro
GPU: GeForce GTX 980
GPU driver version: 344.48
Render mode: DX11, Deferred

Here's the call stack reported in Visual Studio when hitting the "debug" option in the crash dialog.

>	ntdll.dll!7767d062()	Unknown
[Frames below may be incorrect and/or missing, no symbols loaded for ntdll.dll]
mono.dll!mono_jit_info_table_find(_MonoDomain * domain, char * addr) Line 392 C
mono.dll!get_method_from_ip(void * ip) Line 187 C
Unity.exe!StackWalker::ShowCallstackSimple(void * hThread, const _CONTEXT * context) Line 1511 C++
Unity.exe!winutils::ProcessInternalCrash(_EXCEPTION_POINTERS * pExInfo, bool passToDefaultCrashHandler) Line 514 C++
Unity.exe!_ProcessInternalCrash(_EXCEPTION_POINTERS * pExInfo) Line 524 C++
[External Code]
nvwgf2um.dll!58c0c80f() Unknown
[External Code]
nvwgf2um.dll!587c7b92() Unknown
[External Code]
OculusPlugin.dll!55665df0() Unknown
OculusPlugin.dll!55644b35() Unknown
OculusPlugin.dll!5564194d() Unknown
OculusPlugin.dll!5564303a() Unknown
Unity.exe!PluginsRenderMarker(int marker) Line 154 C++
Unity.exe!GfxDevice::InsertCustomMarker(int marker) Line 957 C++
Unity.exe!GfxDeviceWorker::RunCommand(ThreadedStreamBuffer & stream) Line 1277 C++
Unity.exe!GfxDeviceWorker::RunGfxDeviceWorker(void * data) Line 215 C++
Unity.exe!Thread::RunThreadWrapper(void * ptr) Line 40 C++
[External Code]


I can't post the project publicly. I'm happy to send it to someone at Oculus privately if it would be helpful.

Is there anything I can try on my side to debug this further?

12 Replies

Replies have been turned off for this discussion