java.lang.RuntimeException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • Description: While testing KitchenSink I noticed some new log behavior I hadn't seen in other passes. I was able to find a reproducible case by launching the Mashups>SOAP test, hitting back and launching the test again. By approximately the third attempt, the following will appear in the log: 07-19 11:22:28.157: WARN/MessageQueue(2534): Handler{40acfa10} sending message to a Handler on a dead thread 07-19 11:22:28.157: WARN/MessageQueue(2534): java.lang.RuntimeException: Handler{40acfa10} sending message to a Handler on a dead thread 07-19 11:22:28.157: WARN/MessageQueue(2534): at android.os.MessageQueue.enqueueMessage(MessageQueue.java:196) 07-19 11:22:28.157: WARN/MessageQueue(2534): at android.os.Handler.sendMessageAtTime(Handler.java:457) 07-19 11:22:28.157: WARN/MessageQueue(2534): at android.os.Handler.sendMessageDelayed(Handler.java:430) 07-19 11:22:28.157: WARN/MessageQueue(2534): at android.os.Handler.post(Handler.java:248) 07-19 11:22:28.157: WARN/MessageQueue(2534): at org.appcelerator.titanium.kroll.KrollCallback.callAsync(KrollCallback.java:162) 07-19 11:22:28.157: WARN/MessageQueue(2534): at org.appcelerator.titanium.kroll.KrollCallback.callAsync(KrollCallback.java:96) 07-19 11:22:28.157: WARN/MessageQueue(2534): at org.appcelerator.titanium.kroll.KrollCallback.callAsync(KrollCallback.java:91) 07-19 11:22:28.157: WARN/MessageQueue(2534): at ti.modules.titanium.network.TiHTTPClient.fireCallback(TiHTTPClient.java:471) 07-19 11:22:28.157: WARN/MessageQueue(2534): at ti.modules.titanium.network.TiHTTPClient.fireCallback(TiHTTPClient.java:462) 07-19 11:22:28.157: WARN/MessageQueue(2534): at ti.modules.titanium.network.TiHTTPClient.setReadyState(TiHTTPClient.java:494) 07-19 11:22:28.157: WARN/MessageQueue(2534): at ti.modules.titanium.network.TiHTTPClient$ClientRunnable.run(TiHTTPClient.java:1013) 07-19 11:22:28.157: WARN/MessageQueue(2534): at java.lang.Thread.run(Thread.java:1019) Steps to Reproduce: 1) Launch KS, built with 1.7.2 2) Ensure you are loggings 3) Navigate to Mashups>SOAP 4) Tap "back" 5) Repeat steps 3 and 4 until you see the log output Result: Warnings logged: java.lang.RuntimeException: Handler{40aa1810} sending message to a Handler on a dead thread Expected results: No warnings logged
    via by Eric Merriman ,
  • Description: While testing KitchenSink I noticed some new log behavior I hadn't seen in other passes. I was able to find a reproducible case by launching the Mashups>SOAP test, hitting back and launching the test again. By approximately the third attempt, the following will appear in the log: 07-19 11:22:28.157: WARN/MessageQueue(2534): Handler{40acfa10} sending message to a Handler on a dead thread 07-19 11:22:28.157: WARN/MessageQueue(2534): java.lang.RuntimeException: Handler{40acfa10} sending message to a Handler on a dead thread 07-19 11:22:28.157: WARN/MessageQueue(2534): at android.os.MessageQueue.enqueueMessage(MessageQueue.java:196) 07-19 11:22:28.157: WARN/MessageQueue(2534): at android.os.Handler.sendMessageAtTime(Handler.java:457) 07-19 11:22:28.157: WARN/MessageQueue(2534): at android.os.Handler.sendMessageDelayed(Handler.java:430) 07-19 11:22:28.157: WARN/MessageQueue(2534): at android.os.Handler.post(Handler.java:248) 07-19 11:22:28.157: WARN/MessageQueue(2534): at org.appcelerator.titanium.kroll.KrollCallback.callAsync(KrollCallback.java:162) 07-19 11:22:28.157: WARN/MessageQueue(2534): at org.appcelerator.titanium.kroll.KrollCallback.callAsync(KrollCallback.java:96) 07-19 11:22:28.157: WARN/MessageQueue(2534): at org.appcelerator.titanium.kroll.KrollCallback.callAsync(KrollCallback.java:91) 07-19 11:22:28.157: WARN/MessageQueue(2534): at ti.modules.titanium.network.TiHTTPClient.fireCallback(TiHTTPClient.java:471) 07-19 11:22:28.157: WARN/MessageQueue(2534): at ti.modules.titanium.network.TiHTTPClient.fireCallback(TiHTTPClient.java:462) 07-19 11:22:28.157: WARN/MessageQueue(2534): at ti.modules.titanium.network.TiHTTPClient.setReadyState(TiHTTPClient.java:494) 07-19 11:22:28.157: WARN/MessageQueue(2534): at ti.modules.titanium.network.TiHTTPClient$ClientRunnable.run(TiHTTPClient.java:1013) 07-19 11:22:28.157: WARN/MessageQueue(2534): at java.lang.Thread.run(Thread.java:1019) Steps to Reproduce: 1) Launch KS, built with 1.7.2 2) Ensure you are loggings 3) Navigate to Mashups>SOAP 4) Tap "back" 5) Repeat steps 3 and 4 until you see the log output Result: Warnings logged: java.lang.RuntimeException: Handler{40aa1810} sending message to a Handler on a dead thread Expected results: No warnings logged
    via by Eric Merriman ,
  • How to send a message to Handler on a dead thread
    via by Unknown author,
  • [android] app reloads consistently
    via GitHub by ggordan
    ,
    • java.lang.RuntimeException: Handler{40acfa10} sending message to a Handler on a dead thread at android.os.MessageQueue.enqueueMessage(MessageQueue.java:196) at android.os.Handler.sendMessageAtTime(Handler.java:457) at android.os.Handler.sendMessageDelayed(Handler.java:430) at android.os.Handler.post(Handler.java:248) at org.appcelerator.titanium.kroll.KrollCallback.callAsync(KrollCallback.java:162) at org.appcelerator.titanium.kroll.KrollCallback.callAsync(KrollCallback.java:96) at org.appcelerator.titanium.kroll.KrollCallback.callAsync(KrollCallback.java:91) at ti.modules.titanium.network.TiHTTPClient.fireCallback(TiHTTPClient.java:471) at ti.modules.titanium.network.TiHTTPClient.fireCallback(TiHTTPClient.java:462) at ti.modules.titanium.network.TiHTTPClient.setReadyState(TiHTTPClient.java:494) at ti.modules.titanium.network.TiHTTPClient$ClientRunnable.run(TiHTTPClient.java:1013) at java.lang.Thread.run(Thread.java:1019)

    Users with the same issue

    Indri Yunita
    23 times, last one,
    filpgame
    7 times, last one,
    mukky
    1 times, last one,
    danleyb2Interintel
    1 times, last one,
    NedGr8
    1 times, last one,
    27 more bugmates