[0.6.2 for PC] Crash at program startup

[drash]

After building an empty project with a cube and a light using the new legacy Unity integration 0.6.2, the app will crash 100% of the time at startup. Edit: This is with Unity 4.6.7p3.

• Same thing after putting 0.6.2 into an existing project that previously had integration 0.6.1.


• Same results whether I'm using Runtime 0.6.0.1 or Runtime 0.7.0.0. Demo scene works fine in either Runtime.


• Tried rebooting, restarting OVRservice, etc.


• Tracker camera working properly.


• DK2 is on when attempting to run program.


• Win8 64-bit, GTX 970, driver 355.83.


• Nothing is written to OVRServer log at the time of a crash. No exception or deadlock reports.

The crash looks like a "X has stopped working" dialog box. When "showing more details", this is the error:

Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	1.exe
  Application Version:	4.6.7.47249
  Application Timestamp:	55ba0874
  Fault Module Name:	ntdll.dll
  Fault Module Version:	6.3.9600.17936
  Fault Module Timestamp:	55a68dd1
  Exception Code:	c0000005
  Exception Offset:	00040fb2
  OS Version:	6.3.9600.2.0.0.256.48
  Locale ID:	1033
  Additional Information 1:	4a2f
  Additional Information 2:	4a2f9f742bbdce72ce8ef04cd0aceb8b
  Additional Information 3:	3047
  Additional Information 4:	30472859f0e38697c376dc7854217f95

Attached are the Unity output log & riftdiagnostic.txt.

[vrdaveb]

This sounds like a server deadlock. During one of those, the app would freeze for about 30s without responding and then exit or render at an extremely low frame rate. Do you know what kind of crash it is (access violation, exception, etc)? Do you see any warnings in the server log? Does the demo scene continue to respond if if you leave it running in the background while running your app?

[drash]

"vrdaveb" wrote:
This sounds like a server deadlock. During one of those, the app would freeze for about 30s without responding and then exit or render at an extremely low frame rate. Do you know what kind of crash it is (access violation, exception, etc)? Do you see any warnings in the server log? Does the demo scene continue to respond if if you leave it running in the background while running your app?

The kind of crash is simply a "X has stopped working" error dialog. Crashes immediately at startup, no delay. 100% repeatable.
Nothing added to log in AppData\Local\Oculus at the time of crash. No deadlock or exception logs generated in AppData\Local\Oculus\OVRServer.
If I leave it running, demo scene continues running fine in background during all of this.

[cybereality]

Can you post the test build you said with just a cube or whatever? I'd like to see if it crashes on my machine.

[drash]

Here's a test build (8MB zipped): TestCrash062.zip