All geek questions in one place

A thread exiting with an uncaught exception

my application is almost done. Now I'm just making a correction. I encounter the problem that sometimes I accidentally (not always at the same time or after the same actions are performed) so that my application crashes. Logcat just tells me

threadid=11 thread eixiting with uncaught exception (group=0x4134d2a0)

But there is no “caused” by what usually comes, so I can actually catch the exception. When it crashes (by accident), this is written to my console.

 [2013-10-22 15:39:36 - ddms] null java.lang.NullPointerException at com.android.ddmlib.Client.read(Client.java:698) at com.android.ddmlib.MonitorThread.processClientActivity(MonitorThread.java:311) at com.android.ddmlib.MonitorThread.run(MonitorThread.java:263) [2013-10-22 15:39:36 - ddms] null java.lang.NullPointerException at com.android.ddmlib.Client.read(Client.java:698) at com.android.ddmlib.MonitorThread.processClientActivity(MonitorThread.java:311) at com.android.ddmlib.MonitorThread.run(MonitorThread.java:263)

But these are not my classes. How can I catch the exception? Keep in mind that I cannot post all the code here. This is, firstly, too much, and I am not allowed ... The application accidentally crashes. I don’t know why and how to handle it. Any suggestions?

Now I am launching a galaxy note application.

+6
source share
2 answers

These errors occur when something is wrong with the communication between the DDMS and the device. They are generally harmless, but you can solve them by restarting the ADB server:

 adb kill-server adb start-server

If you are using an emulator and this does not solve the problem, try deleting and re-creating the AVD.

+5
source

Does your logarithm have the text "Called ..."? It should point to the code that caused the error.

-1
source

Source: https://habr.com/ru/post/956488/

More articles:


All Articles