Forum Discussion
galopin
9 years agoHeroic Explorer
OculusDebugTools.exe crash (with callstack)
Hi,
So i do not yet have my CV1, but i have the runtime 1.3 installed, and tried to set the debug hmd to cv1 in the debug tool, immediate crash :(
So i do not yet have my CV1, but i have the runtime 1.3 installed, and tried to set the debug hmd to cv1 in the debug tool, immediate crash :(
> ntdll.dll!RtlpLowFragHeapFree() Unknown
ntdll.dll!RtlFreeHeap() Unknown
msvcr120.dll!free(void * pBlock) Line 51 C
OculusDebugTool.exe!00007ff7445f2648() Unknown
OculusDebugTool.exe!00007ff7445fd7cd() Unknown
OculusDebugTool.exe!00007ff7445f65c1() Unknown
OculusDebugTool.exe!00007ff7445f8f5a() Unknown
OculusDebugTool.exe!00007ff7445fc77d() Unknown
OculusDebugTool.exe!00007ff744419430() Unknown
OculusDebugTool.exe!00007ff7444013f6() Unknown
OculusDebugTool.exe!00007ff74445d3ae() Unknown
OculusDebugTool.exe!00007ff74445d27e() Unknown
OculusDebugTool.exe!00007ff74445d475() Unknown
OculusDebugTool.exe!00007ff7444009f1() Unknown
OculusDebugTool.exe!00007ff7444831ab() Unknown
OculusDebugTool.exe!00007ff7444632f9() Unknown
OculusDebugTool.exe!00007ff744521d5e() Unknown
OculusDebugTool.exe!00007ff744610381() Unknown
kernel32.dll!BaseThreadInitThunk() Unknown
ntdll.dll!RtlUserThreadStart() Unknown
16 Replies
- galopinHeroic Explorerdamned i hate the new interface, cyber if you are here can you move that to the dev section :)
- gundeepsinghHonored GuestSame issue here!
- VrallyProtegeI have the same issue.
- mattnewportProtegeCrashes for me if I try and turn the performance HUD on too.
- jhericoAdventurerI tried running it and wanted to test turning off the rendering of layer 0. It apparently managed to do so but crashed immediately, leaving me with no way to turn it back on (it defaults in the app to being 'on' even though it's not, and I couldn't toggle it off and back on again because it would crash whenever I turned it off). I had to restart the Oculus service to get stuff visible again.
- Anonymous
I have the same issue. It is hard to disable the OSD later after the crash because it can not be switched to None by the Oculus Debug Tool. PC restart required :-(. Anybody form Oculus Developers listening ??? I use 1.3.1 runtime ...
- galopinHeroic ExplorerIn my app, i just set it to off on exit or the home had it stuck.
No need for a reboot, just write a small executable to update the debug display :) - galopinHeroic ExplorerBut yes, it is lame to see so many people crashing on that. It probably should be easy to catch it prior to launch, and it is relevant to the QA process within Oculus :t
- YbalridExpert ProtegeThis window also crash if you set a debug hmd (for rendering with no Oculus device attached)
- galopinHeroic Explorer@Ybalrid it was the crash of my original post ^^ the debug display thing came after :)
Quick Links
- Horizon Developer Support
- Quest User Forums
- Troubleshooting Forum for problems with a game or app
- Quest Support for problems with your device
Other Meta Support
Related Content
- 5 months ago
- 2 years ago
- 2 years ago