diablodale
commented
7 years ago Thank you. I have a few requests to better understand, please.
This may be a known crash in Microsoft's drivers. I write about this in the 2nd bullet. https://github.com/diablodale/dp.kinect2/wiki#known-issues-limitations-report-problems There was some forum chatter about it at https://social.msdn.microsoft.com/Forums/en-US/10425cc3-d732-4163-85a5-7f6c4ae983c0/kinect20facedll-crashes-in-repetitive-testing-of-3d-model-features?forum=kinectv2sdk#6562810d-05f1-434f-9357-1beb48f0c957 and some private emails between Microsoft and I that I can't share.
The crash I isolated and write above above appears similar to yours. Mine occurred when I was looping prerecorded material, not in a live scenario. This known crash occurs when the Kinect2 HD face features are used. In your example patch, you use only one option that activates the HD face codepath: @facecolors
I reviewed the crash details. Good bug report! :-) The crash in your report is caused within Microsoft's driver code Kinect20.Face.x64.dll. You can see that on the Faulting module name line in your report. The type of crash is Exception code 0xc0000005 also from your report. 0xc0000005 is the Windows OS error STATUS_ACCESS_VIOLATION. This means that Microsoft's code in Kinect20.Face.x64.dll is trying to access a place in memory that doesn't exist, is invalid, doesn't have security permission, etc. There is definitely a bug in their code.
It may be possible that my code is sending something invalid to their driver and they do not gracefully handle invalid data. In this case, both Microsoft and I have a bug.
I tried many approaches in 2014 with the crash I isolated. The forum writes about that. I found that I could prevent dp.kinect2 crashing using overly strong error handling in my code. But it wasn't very useful. Why? Because when I did that, the Kinect2 drivers and subsystem still crashed. When the crash cascaded upward to my code, I was able to catch the crash to prevent dp.kinect2 itself from crashing. That left dp.kinect2 in a good state but the entire Kinect2 drivers/subsystem in a corrupt state. It wasn't helpful. This kind of behavior within Microsoft's Kinect2 code suggests a bug that I might not be able to control. Still, I'm happy to continue investigating.
I suspect (still unclear) that the crash you are experiencing and the known crash I isolated are the same bugs. It help further isolate, I have two requests of you:
- In your first paragraph, you write "with multiple people moving in front". Did the crash you isolated occur with two dp.kinect2 with live people for 20 minutes? Or, was this a recording of multiple people that you looped for 20 minutes?
- If you remove/disable @facecolors on the dp.kinect2 (top level of your patch) in your example patch, do you experience the crash? And if it does crash, is this with live people or looped recording?
aartcore
Hey,
Just want to report a crash/bug, looks like that I finally found how to prevent it crashing. It looks like if i've two dp.kinect2 objects with @faceprop 1 @faces 1 it gets a conflict running for like 15 / 20 minutes (with (multiple) people moving in front of the kinect-camera).
I stripped down my patch to search for the crashing element. When I run this patch it crashes in 15 / 20 minutes. Now I removed the in first (left) dp.kinect2 the face arguments and now it still running after a night testing (in combination with looping pre-recorded material in Kinect Studio).
I attached also the crashreports which I got: Or with a fault in the Kinect20.Face.x64.dll or with KERNELBASE.dll (most of the time).
If you want more info, i'm happy to help!
dp.kinect2 v1.1.20160922.0 Win64 Max 7.3.3 (64-bit) Windows 10 - Mac Mini i7 3.0 GHz
crashreports:
Faulting application name: Max.exe, version: 7.3.3.36780, time stamp: 0x58b6c502 Faulting module name: Kinect20.Face.x64.dll, version: 2.0.1410.19000, time stamp: 0x54441cc5 Exception code: 0xc0000005 Fault offset: 0x00000000000a4335 Faulting process id: 0x120c Faulting application start time: 0x01d2e5ae775e1bd0 Faulting application path: C:\Program Files\Cycling '74\Max 7\Max.exe Faulting module path: C:\Users\wincore\Documents\Max 7\Packages\dp.kinect2\externals\Kinect20.Face.x64.dll Report Id: f6895360-25a9-4372-aa6c-173bf0c1c804 Faulting package full name: Faulting package-relative application ID:
Faulting application name: Max.exe, version: 7.3.3.36780, time stamp: 0x58b6c502 Faulting module name: KERNELBASE.dll, version: 10.0.10586.873, time stamp: 0x58d9fd3a Exception code: 0xe06d7363 Fault offset: 0x0000000000071f28 Faulting process id: 0x1730 Faulting application start time: 0x01d2e5b4062a9b80 Faulting application path: C:\Program Files\Cycling '74\Max 7\Max.exe Faulting module path: C:\Windows\system32\KERNELBASE.dll Report Id: 5944e43e-4746-49f6-85c4-023306ecd904 Faulting package full name: Faulting package-relative application ID:
test-patch: