Segmentation fault when running with realsense D415?

[AIBluefisher]

Hi, @Nicien

I compiled InfiniTAM V3.0 with realsense SDK 2.0, but I got segmentation fault every time after it captures the 102-th frame. I'm not sure what's wrong. Besides, I get confused of how to set the calibration file for realsense. Because the realsense D415 has two imagers and a IR for depth image capture, and a RGB sensor for RGB image capture, like the picture shown below:

After I calibrate the realsense D415, the calibration information is:

Can you help me?

[AIBluefisher]

@sgolodetz
Hi, this commit does fix this bug. But infinitam cannot reconstruct the mesh as the window shows nothing.

[sgolodetz]

@AIBluefisher The fact that the pull request is number 116 is unrelated to addressing issue number 116 - not sure why GitHub links the two in the way that it does. I was just merging some of Tommaso's code that allows you to read in PNG images without having to link with libpng.

Not sure why the RealSense is giving you a segmentation fault - have you tried running it through the debugger to find out where it's crashing? That might give us a bit more information to figure out what's going on.

[AIBluefisher]

@sgolodetz Sorry, after trying several times when running with realsense, the issue appears again after processing 121 frames, even though built with OpenCV. I'm trying to figure it out, and I will give you some debug information.