Forum Discussion
Questions about error messages
So my OpenGL DK 2 programs runs now in SDK direct mode and Windows 8.1. I can see it working on the screen and head movements are being tracked. However, nothing shows up in my Rift - the LED is yellow and does not turn blue, so I still have work to do. (My Rift does work fine in direct mode for the Oculus World Demo program.) I have 3 questions here (I'm using Visual C++ 2010):
Question 1. When I abort my program in debug mode I see the following messages
Debug: Failed to open file: C:\Users\Max\AppData\Local/Oculus/Devices.json
Debug: Using profile Max
Debug: [SharedMemory] Creating factory
Debug: [SharedMemory] Creating shared memory region: OVRObject00 > 1184 bytes
Debug: GL_VERSION: 4.1.0 NVIDIA 344.75
Debug: [HSWDisplay] Display()
Debug: [HSWDisplay GL] DisplayInternal()
Debug: GL_VERSION: 4.4.0 NVIDIA 344.75
The program '[12224] Space2011.exe: Native' has exited with code 0 (0x0).
I see no Devices.json file in the above user directory. Should there be one?
There are files ConfigUtilSettings.json, ProfileDB.json, NetServer.cfg, and lots of ServerLog files.
Question 2. The latest ServerLog file shows
{ERR-027} [WatchDogObserver] Deadlock detected: LongPoll{ERR-027} [WatchDogObserver] Deadlock detected: DeviceManager{ERR-027} [WatchDogObserver] Deadlock detected: NetServer
What does that mean?
Question 3. When I exit my program in debug mode I get memory leaks. I have NO memory leaks
when the oculus rift stuff is not activated. I have looked very hard in my code but have not seen
where I might be causing this. Something is not being cleaned up in the oculus code even though
I call ovr_Shutdown(); Where are these leaks coming from?
Thanks for any ideas on this.
Question 1. When I abort my program in debug mode I see the following messages
Debug: Failed to open file: C:\Users\Max\AppData\Local/Oculus/Devices.json
Debug: Using profile Max
Debug: [SharedMemory] Creating factory
Debug: [SharedMemory] Creating shared memory region: OVRObject00 > 1184 bytes
Debug: GL_VERSION: 4.1.0 NVIDIA 344.75
Debug: [HSWDisplay] Display()
Debug: [HSWDisplay GL] DisplayInternal()
Debug: GL_VERSION: 4.4.0 NVIDIA 344.75
The program '[12224] Space2011.exe: Native' has exited with code 0 (0x0).
I see no Devices.json file in the above user directory. Should there be one?
There are files ConfigUtilSettings.json, ProfileDB.json, NetServer.cfg, and lots of ServerLog files.
Question 2. The latest ServerLog file shows
{ERR-027} [WatchDogObserver] Deadlock detected: LongPoll{ERR-027} [WatchDogObserver] Deadlock detected: DeviceManager{ERR-027} [WatchDogObserver] Deadlock detected: NetServer
What does that mean?
Question 3. When I exit my program in debug mode I get memory leaks. I have NO memory leaks
when the oculus rift stuff is not activated. I have looked very hard in my code but have not seen
where I might be causing this. Something is not being cleaned up in the oculus code even though
I call ovr_Shutdown(); Where are these leaks coming from?
Thanks for any ideas on this.
3 Replies
- I recall hearing about the deadlock before and it was suggested you try unplugging the camera.
Can you see if that helps at all? - No more log file was created when I unplugged the camera and I got no more deadlock messages.
Aside from the messages, I am not aware of any problem. However, I would like to use the camera, so that the Rift developers need to check that out.
What about the missing devices.json file?
My memory leakage all came from:
OVR_String.cpp
OVR_Allocator.cpp
OVR_ContainerAllocator.cpp
This is probably because I had to include the OVR_Stereo.h file and created some render info files which used the String class. The Oculus Rift software needs to clean up after itself - I can't do it. - I installed the Oculus software on a Windows 7 computer today to see if anything would be different. My program does not show any video on the Rift there either (the light stays orange) but I did notice that in Windows 7 there are 2 additional files stored: devices.json and profiles.json. These did not get created in Windows 8.1. Strange!
