Libgdx Android – Process has died with no erros - android

In the middle of the game, it closes without showing any erros.
How to identify what is causing this behavior?
I removed all exit commands on the code and still closes.
LogCat:
All Messages:
05-20 09:21:16.785: I/ActivityManager(27603): Process com.xxxx.yyyy.android (pid 13684) has died.
On the process (PID 13684):
No errors.
No warnings.
No messages, just the normal game System.out
If I just close the game, the message on LogCat is the same.
Another device shows the errors on logCat of the process:
Note: the file numbers/2.png is ok and normally used on the Game.
05-21 08:00:54.398: E/libutils.threads(14116): androidCreateRawThreadEtc failed (entry=0x4017cf20, res=11, errno=0)
05-21 08:00:54.398: E/libutils.threads(14116): (android threadPriority=-16)
05-21 08:00:54.708: A/libc(14116): malloc size: 695556
05-21 08:00:55.218: E/AndroidRuntime(14116): FATAL EXCEPTION: GLThread 15797
05-21 08:00:55.218: E/AndroidRuntime(14116): Process: com.dsgames.combinations2048.android, PID: 14116
05-21 08:00:55.218: E/AndroidRuntime(14116): com.badlogic.gdx.utils.GdxRuntimeException: Couldn't load file: numbers/2.png
05-21 08:00:55.218: E/AndroidRuntime(14116): at com.badlogic.gdx.graphics.Pixmap.<init>(Pixmap.java:148)
05-21 08:00:55.218: E/AndroidRuntime(14116): at com.badlogic.gdx.graphics.TextureData$Factory.loadFromFile(TextureData.java:98)
05-21 08:00:55.218: E/AndroidRuntime(14116): at com.badlogic.gdx.graphics.Texture.<init>(Texture.java:100)
05-21 08:00:55.218: E/AndroidRuntime(14116): at com.badlogic.gdx.graphics.Texture.<init>(Texture.java:92)
05-21 08:00:55.218: E/AndroidRuntime(14116): at com.badlogic.gdx.graphics.Texture.<init>(Texture.java:88)
05-21 08:00:55.218: E/AndroidRuntime(14116): at com.xxxx.yyyy.GameScreen.touchDown(GameScreen.java:2573)
05-21 08:00:55.218: E/AndroidRuntime(14116): at com.badlogic.gdx.InputMultiplexer.touchDown(InputMultiplexer.java:90)
05-21 08:00:55.218: E/AndroidRuntime(14116): at com.badlogic.gdx.backends.android.AndroidInput.processEvents(AndroidInput.java:375)
05-21 08:00:55.218: E/AndroidRuntime(14116): at com.badlogic.gdx.backends.android.AndroidGraphics.onDrawFrame(AndroidGraphics.java:470)
05-21 08:00:55.218: E/AndroidRuntime(14116): at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1527)
05-21 08:00:55.218: E/AndroidRuntime(14116): at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1244)
05-21 08:00:55.218: E/AndroidRuntime(14116): Caused by: java.io.IOException: Error loading pixmap: decoder init failed for stream
05-21 08:00:55.218: E/AndroidRuntime(14116): at com.badlogic.gdx.graphics.g2d.Gdx2DPixmap.<init>(Gdx2DPixmap.java:90)
05-21 08:00:55.218: E/AndroidRuntime(14116): at com.badlogic.gdx.graphics.Pixmap.<init>(Pixmap.java:146)
05-21 08:00:55.218: E/AndroidRuntime(14116): ... 10 more
05-21 08:00:59.698: E/AndroidGraphics(14116): waiting for pause synchronization took too long; assuming deadlock and killing
I discovered the problem. Every click on the screen, I created a new texture without making a dispose of the others. It was memory usage issue.
I think the line A / libc (14116): malloc size: 695 556 indicates this.
The question that remains is:
Why in one device did not generate error, only closed the game?

Related

Meidapipe hands livestreaming: FATAL EXCEPTION: ExternalTextureConverter

enter image description here
This is an peoject imported from Mediapipe's git :project:https://github.com/google/mediapipe/tree/master/mediapipe/examples/android/solutions
There're three modes:static image, video, live-camera. Only static image mode can run successfully, video mode and live mode will crash and have erros like this:
`*E/BufferQueueProducer: [SurfaceTexture-1-4220-0](id:107c00000000,api:4,p:431,c:4220) dequeueBuffer: BufferQueue has been abandoned
E/BufferQueueProducer: [SurfaceTexture-1-4220-0](id:107c00000000,api:4,p:431,c:4220) queueBuffer: BufferQueue has been abandoned
D/GlThread: Stopping GL thread ExternalTextureConverter
E/AndroidRuntime: FATAL EXCEPTION: ExternalTextureConverter
Process: com.google.mediapipe.apps.hands, PID: 4220
java.lang.RuntimeException: Framebuffer not complete, status=36054
at com.google.mediapipe.glutil.GlThread.bindFramebuffer(GlThread.java:114)
at com.google.mediapipe.components.ExternalTextureConverter$RenderThread.createFrame(ExternalTextureConverter.java:477)
at com.google.mediapipe.components.ExternalTextureConverter$RenderThread.nextOutputFrame(ExternalTextureConverter.java:506)
at com.google.mediapipe.components.ExternalTextureConverter$RenderThread.renderNext(ExternalTextureConverter.java:434)
at com.google.mediapipe.components.ExternalTextureConverter$RenderThread.lambda$onFrameAvailable$0$com-google-mediapipe-components-ExternalTextureConverter$RenderThread(ExternalTextureConverter.java:386)
at com.google.mediapipe.components.ExternalTextureConverter$RenderThread$$ExternalSyntheticLambda0.run(Unknown Source:4)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:223)
at com.google.mediapipe.glutil.GlThread.run(GlThread.java:141)
E/BufferQueueProducer: [SurfaceTexture-1-4220-0](id:107c00000000,api:4,p:431,c:4220) queueBuffer: BufferQueue has been abandoned*`
Is there anybody who has met this erro?And how to solve it.

How to detect Bluetooth RFCOM channel crash from application android

I have an application where sometimes Bluetooth channels are crashing from OS layer and then Bluetooth channel not start working again until phone rebooted. As its a OS layer crash I can't detect/handle it from my application. Here is the crash:
02-20 05:32:45.751: I/BluetoothServiceJni(20779): SOCK FLAG = 3 ***********************
02-20 05:32:45.751: E/BluetoothServiceJni(20779): Socket listen failed: 2
02-20 05:32:45.751: E/BluetoothAdapterService(1918354448)(20779): Failed to create socket channel
02-20 05:32:45.751: E/BluetoothSocketThread(762): Failed to listen for Bluetooth server socket connect.
02-20 05:32:45.751: E/BluetoothSocketThread(762): java.io.IOException: Error: -1
02-20 05:32:45.751: E/BluetoothSocketThread(762): at android.bluetooth.BluetoothAdapter.createNewRfcommSocketAndRecord(BluetoothAdapter.java:1245)
02-20 05:32:45.751: E/BluetoothSocketThread(762): at android.bluetooth.BluetoothAdapter.listenUsingRfcommWithServiceRecord(BluetoothAdapter.java:1161)
02-20 05:32:45.751: E/BluetoothSocketThread(762): at com.google.glass.bluetooth.BluetoothAdapter.listenUsingRfcommWithServiceRecord(BluetoothAdapter.java:148)
02-20 05:32:45.751: E/BluetoothSocketThread(762): at com.google.glass.bluetooth.companion.BluetoothSocketThread.runInternally(BluetoothSocketThread.java:67)
02-20 05:32:45.751: E/BluetoothSocketThread(762): at com.google.glass.bluetooth.companion.CompanionServerThread.run(CompanionServerThread.java:61)
02-20 05:32:45.761: W/BluetoothAdapter(762): getBluetoothService() called with no BluetoothManagerCallback
My question, is there any way to detect Bluetooth channel OS related crash from my applicaiton.
Is it possible to detect the crash using fabric crashlytics native support or anything else?

NullReferenceException on Xamarin Droid App startup

I am facing a NullReferenceException when starting an Xamarin Android App via Visual Studio 2015.
It is thrown after leaving the OnCreate() in my main activity, but I do not know where and why. How can find more information about this error?
The Debug output is like this:
05-21 20:18:51.643 D/OpenGLRenderer(25574): Use EGL_SWAP_BEHAVIOR_PRESERVED: true
05-21 20:18:51.651 D/Atlas (25574): Validating map...
Unhandled Exception:
System.NullReferenceException: Object reference not set to an instance of an object
Exception:
System.NullReferenceException: Object reference not set to an instance of an object
05-21 20:19:37.436 D/Mono (25574): DllImport attempting to load: '/system/lib/liblog.so'.
05-21 20:19:37.436 D/Mono (25574): DllImport loaded library '/system/lib/liblog.so'.
05-21 20:19:37.436 D/Mono (25574): DllImport searching in: '/system/lib/liblog.so' ('/system/lib/liblog.so').
05-21 20:19:37.436 D/Mono (25574): Searching for '__android_log_print'.
05-21 20:19:37.436 D/Mono (25574): Probing '__android_log_print'.
05-21 20:19:37.437 D/Mono (25574): Found as '__android_log_print'.
05-21 20:19:37.450 I/MonoDroid(25574): UNHANDLED EXCEPTION:
05-21 20:19:37.454 I/MonoDroid(25574): System.NullReferenceException: Object reference not set to an instance of an object
05-21 20:19:37.454 I/MonoDroid(25574): at Xamarin.Forms.Platform.Android.KeyboardManager.HideKeyboard (Android.Views.View inputView, Boolean overrideValidation) [0x00000] in C:\BuildAgent3\work\aad494dc9bc9783\Xamarin.Forms.Platform.Android\KeyboardManager.cs:14
05-21 20:19:37.454 I/MonoDroid(25574): at Xamarin.Forms.Platform.Android.FormsApplicationActivity.OnPause () [0x00000] in C:\BuildAgent3\work\aad494dc9bc9783\Xamarin.Forms.Platform.Android\FormsApplicationActivity.cs:153
05-21 20:19:37.455 I/MonoDroid(25574): at Android.App.Activity.n_OnPause (IntPtr jnienv, IntPtr native__this) [0x00009] in /Users/builder/data/lanes/3236/ee215fc9/source/monodroid/src/Mono.Android/platforms/android-23/src/generated/Android.App.Activity.cs:4046
05-21 20:19:37.455 I/MonoDroid(25574): at (wrapper dynamic-method) System.Object:5c198319-5b9a-4152-9518-5aa3ce7cab6e (intptr,intptr)
05-21 20:19:37.476 W/art (25574): JNI RegisterNativeMethods: attempt to register 0 native methods for md52ce486a14f4bcd95899665e9d932190b.JavaProxyThrowable
An unhandled exception occured.
05-21 20:19:38.791 E/mono (25574):
05-21 20:19:38.791 E/mono (25574): Unhandled Exception:
05-21 20:19:38.791 E/mono (25574): System.NullReferenceException: Object reference not set to an instance of an object
05-21 20:19:38.791 E/mono (25574): at (wrapper dynamic-method) System.Object:5c198319-5b9a-4152-9518-5aa3ce7cab6e (intptr,intptr)
05-21 20:19:38.791 E/mono (25574): at (wrapper native-to-managed) System.Object:5c198319-5b9a-4152-9518-5aa3ce7cab6e (intptr,intptr)
05-21 20:19:38.792 E/mono-rt (25574): [ERROR] FATAL UNHANDLED EXCEPTION: System.NullReferenceException: Object reference not set to an instance of an object
05-21 20:19:38.792 E/mono-rt (25574): at (wrapper dynamic-method) System.Object:5c198319-5b9a-4152-9518-5aa3ce7cab6e (intptr,intptr)
05-21 20:19:38.792 E/mono-rt (25574): at (wrapper native-to-managed) System.Object:5c198319-5b9a-4152-9518-5aa3ce7cab6e (intptr,intptr)
referenceTable GDEF length=670 1
referenceTable GSUB length=7202 1
referenceTable GPOS length=24560 1
I know it's been a while but perhaps I can help someone in the future. Something similar happened to me when I accidentally removed the initiation of my App.Current.Mainpage while the app was starting up. Silly mistake that leads to an unhelpful error message.
Got the idea on where my problem was from here: https://bugzilla.xamarin.com/show_bug.cgi?id=36287

Android "Shutting down VM" with no stacktrace

I have recently faced this issue a lot and I am not able to find any solution to it.
I am constantly getting Shutting down VM and logcat doesn't show any trace of this issue.
06-08 20:34:25.288 20416-20416/my.package.dev D/app_BaseRecyclerView﹕ onCreateViewHolder begins
06-08 20:34:25.324 20416-20416/my.package.dev D/AndroidRuntime﹕ Shutting down VM
06-08 20:34:30.969 20416-20425/my.package.dev I/art﹕ Thread[5,tid=20425,WaitingInMainSignalCatcherLoop,Thread*=0xb4a33800,peer=0x12c000a0,"Signal Catcher"]: reacting to signal 3
06-08 20:34:30.969 20416-20425/my.package.dev I/art﹕ [ 06-08 20:34:31.169 617: 639 I/Process ]
Sending signal. PID: 617 SIG: 3
Do you know how to make the stacktrace visible?
If you are using Google Analytics, try to disable ExceptionReporting if it is set to true

Android Hello World app crashes: IllegalArgumentException from Surface.lockCanvasNative

I am trying to run the simplest Hello World example app and looks like I can crash it even all it does is showing a TextView.
Steps to reproduce: Launch it in the emulator (1.5). Open the app - it shows the text view, then lock the phone by pressing "end call" button. Unlock by pressing "menu", then press "back". App crashes with "The process android.process.acore has stopped unexpectedly..." and Force Close button. It does not happen all the time, but I am able to reproduce it every time after wiping the user data at least.
I wonder if default Hello World is missing a detail which was considered too advanced for a hello world... Such problems with a basic example does not look very encouraging =)
Any idea what detail is missing and how to avoid this crash?
Stack (I've truncated timestamps):
37.478: DEBUG/KeyguardViewMediator(576): wakeWhenReadyLocked(82)
37.481: DEBUG/KeyguardViewMediator(576): handleWakeWhenReady(82)
37.481: DEBUG/KeyguardViewMediator(576): pokeWakelock(5000)
39.110: DEBUG/KeyguardViewMediator(576): pokeWakelock(5000)
39.140: WARN/InputManagerService(576): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy#436e3fc0
40.990: ERROR/IMemory(679): binder=0x238aa8 transaction failed fd=-2147483647, size=0, err=-2147483646 (Unknown error: 2147483646)
40.990: ERROR/IMemory(679): cannot dup fd=-2147483647, size=0, err=-2147483646 (Bad file number)
40.990: ERROR/IMemory(679): cannot map BpMemoryHeap (binder=0x238aa8), size=0, fd=-1 (Bad file number)
40.990: ERROR/Surface(679): Couldn't map Surface's heap (binder=0x238aa8, heap=0x238b00)
40.990: DEBUG/AndroidRuntime(679): Shutting down VM
40.990: WARN/dalvikvm(679): threadid=3: thread exiting with uncaught exception (group=0x4000fe70)
40.990: ERROR/AndroidRuntime(679): Uncaught handler: thread main exiting due to uncaught exception
40.990: ERROR/AndroidRuntime(679): java.lang.IllegalArgumentException
40.990: ERROR/AndroidRuntime(679): at android.view.Surface.lockCanvasNative(Native Method)
40.990: ERROR/AndroidRuntime(679): at android.view.Surface.lockCanvas(Surface.java:196)
40.990: ERROR/AndroidRuntime(679): at android.view.ViewRoot.draw(ViewRoot.java:1175)
40.990: ERROR/AndroidRuntime(679): at android.view.ViewRoot.performTraversals(ViewRoot.java:1030)
40.990: ERROR/AndroidRuntime(679): at android.view.ViewRoot.handleMessage(ViewRoot.java:1482)
40.990: ERROR/AndroidRuntime(679): at android.os.Handler.dispatchMessage(Handler.java:99)
40.990: ERROR/AndroidRuntime(679): at android.os.Looper.loop(Looper.java:123)
40.990: ERROR/AndroidRuntime(679): at android.app.ActivityThread.main(ActivityThread.java:3948)
40.990: ERROR/AndroidRuntime(679): at java.lang.reflect.Method.invokeNative(Native Method)
40.990: ERROR/AndroidRuntime(679): at java.lang.reflect.Method.invoke(Method.java:521)
40.990: ERROR/AndroidRuntime(679): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:782)
40.990: ERROR/AndroidRuntime(679): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:540)
40.990: ERROR/AndroidRuntime(679): at dalvik.system.NativeStart.main(Native Method)
41.000: INFO/Process(576): Sending signal. PID: 679 SIG: 3
41.000: INFO/dalvikvm(679): threadid=7: reacting to signal 3
41.030: ERROR/ActivityThread(576): Failed to find provider info for android.server.checkin
41.030: ERROR/Checkin(576): Error reporting crash: java.lang.IllegalArgumentException: Unknown URL content://android.server.checkin/crashes
41.070: INFO/dalvikvm(679): Wrote stack trace to '/data/anr/traces.txt'
50.940: WARN/ActivityManager(576): Launch timeout has expired, giving up wake lock!
50.980: WARN/ActivityManager(576): Activity idle timeout for HistoryRecord{4366ac40 {com.android.launcher/com.android.launcher.Launcher}}
sounds to me more like something wrong with your emulator. Why dont you delete your emulator and create a new one and try again with a fresh project.
Hope that will help you. BTW why are you using emulator on 1.5?? Start to build applications for min 2.1.
Good luck.

Categories

Resources