Android SIGABRT Signal 6 Camera2
E/OpenGLRenderer: Texture is using 0.00B, count = 1 OffscreenBuffer is using 0.00B, count = 0 Layer is using 0.00B, count = 1 05-14 19:29:30.911 31706-31756/com.package.test A/OpenGLRenderer: Leaked 2 GPU objects! --------- beginning of crash 05-14 19:29:30.912 31706-31756/com.package.test A/libc: Fatal signal 6 (SIGABRT), code -6 in tid 31756 (RenderThread) [ 05-14 19:29:30.919 10376:10376 W/ ] debuggerd: handling request: pid=31706 uid=10371 gid=10371 tid=31756 It seams that the operating system kills the application in debug mode and disables the camera in release mode in some devices because of the SIGABRT signal that detects something is wrong in the RenderThread with my TextureView that holds the camera preview. I just use camera2 inside a Fragment and I tested it in multiple devices. A link with people talking about the problem without a solve: https://issuetracker.google.com/issues/37123764 Devices with the problem reported: Xperia XZ, Xperia X Compact, Xperia Z5 ... Nexus 6P, Nexus 5X... If there's no solve there's any alternative to prevent the camera close at least in the release mode?
Why was this change made to SocketInputBuffer for Ice Cream Sandwich?
Comprehensive list of Splash Screen and Icons for Phonegap
Image classification with opencv
How to get libgdx view from andengine project
Horizontal scrolling between activities in Android
Read QR Code without using other app
Gps,GeoCoding causes app hang in android
Android App Closes on creation?
GridLayout spitting out “inconsistent constraint” debug-level logs
Android DB: Merging Two Databases Using SQL Dumps
Questio about AdMob ad url to application
trouble importing android-remote-stacktrace
ADT rev20 - apps don't install on any AVD
View will get twice at onItemClick
downloading xml from ftp in android
Notification upon ended parsing of web response