libc Fatal issue when camerastreamingmanager.CaptureFrame is called in quick succession

[pili-engineering]

libc Fatal issue when camerastreamingmanager.CaptureFrame is called in quick succession

[gouravd]

on Android 4.4 device, the 2nd consecutive call to CaptureFrame crashes with
A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x801 in tid 32358 (GLThread 5020)

[jpxiong]

Could you please provide more informations ?Thanks.

[gouravd]

Call 1: handler.postDelayed(screenshotThread, 500);
Call 1 always succeeds.

Call 2: handler.postDelayed(screenshotThread, 500);
Call 2 intermittently fails on my Motorola G2 (Android 5.0.1) and always on Micromax Yureka (4.4.4)

If I call handler.postDelayed(screenshotThread) more frequently (like once in every 5 secs) it crashes on my Motorola as well.

This is reproducible even when the onFrameCaptured function is empty,

private Runnable screenshotThread = new Runnable() {
    @Override
    public void run() {
                @Override
                public void onFrameCaptured(Bitmap bmp) {

                }
        };
};

[jpxiong]

Any logs ?

[gouravd]

I/CameraSurfaceRenderer: captureFrame width:272, height:480
A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x801 in tid 32358 (GLThread 5020)

This is the only thing I saw. I will alter my code to reproduce the issue and share the complete logs too Again since the exception is in the native jni code, I am not too sure if any debug logs would be helpful. But I will still share the logs when I generate them

[jpxiong]

More Debug logs will be helpful to handle the issue. Thanks.

[jpxiong]

I think the following way to catch logs will be more effective：

adb shell logcat -v time thread | tee ~/log.log

[gouravd]

So I clicked on a button which called mCameraStreamingManager.captureFrame. Then I started adb logging and then clicked the button again to call mCameraStreamingManager.captureFrame again and it crashed.

Time when the error occurs - 11-17 17:44:19.701

log.txt

[jpxiong]

The log.txt is very valuable for debugging. Thanks.

[jpxiong]

Had been fixed. The next version will contain the PATCH.

[gouravd]

Awesome news. Thanks

[gouravd]

This is solved in 1.4.3