java.lang.RuntimeException: Handler{40acfa10} sending message to a Handler on a dead thread

Appcelerator JIRA | Eric Merriman | 6 years ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    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

    Appcelerator JIRA | 6 years ago | Eric Merriman
    java.lang.RuntimeException: Handler{40acfa10} sending message to a Handler on a dead thread
  2. 0

    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

    Appcelerator JIRA | 6 years ago | Eric Merriman
    java.lang.RuntimeException: Handler{40acfa10} sending message to a Handler on a dead thread
  3. 0

    {html}<div><p>I am getting the following error when a function calling a Ti.Network.createHTTPClient() -&gt; send() is invoked a second time. First time it works well and good</p> <p>WARN/MessageQueue(367): Handler{43f82b30} sending message to a Handler on a dead thread<br> java.lang.RuntimeException: Handler{43f82b30} sending message to a Handler on a dead thread<br></p> <pre> <code>at android.os.MessageQueue.enqueueMessage(MessageQueue.java:179) 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.KrollContext.post(KrollContext.java:123) at org.appcelerator.titanium.kroll.KrollCallback.callAsync(KrollCallback.java:154) at org.appcelerator.titanium.kroll.KrollCallback.callAsync(KrollCallback.java:89) at org.appcelerator.titanium.kroll.KrollCallback.callAsync(KrollCallback.java:84) at ti.modules.titanium.network.TiHTTPClient.fireCallback(TiHTTPClient.java:468) at ti.modules.titanium.network.TiHTTPClient.fireCallback(TiHTTPClient.java:459) at ti.modules.titanium.network.TiHTTPClient.setReadyState(TiHTTPClient.java:491) at ti.modules.titanium.network.TiHTTPClient$ClientRunnable.run(TiHTTPClient.java:989) at java.lang.Thread.run(Thread.java:1096)</code> </pre></div>{html}

    Appcelerator JIRA | 6 years ago | rGyani
    java.lang.RuntimeException: Handler{43f82b30} sending message to a Handler on a dead thread<br></p> <pre> <code>at android.os.MessageQueue.enqueueMessage(MessageQueue.java:179)
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    {html}<div><p>I am getting the following error when a function calling a Ti.Network.createHTTPClient() -&gt; send() is invoked a second time. First time it works well and good</p> <p>WARN/MessageQueue(367): Handler{43f82b30} sending message to a Handler on a dead thread<br> java.lang.RuntimeException: Handler{43f82b30} sending message to a Handler on a dead thread<br></p> <pre> <code>at android.os.MessageQueue.enqueueMessage(MessageQueue.java:179) 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.KrollContext.post(KrollContext.java:123) at org.appcelerator.titanium.kroll.KrollCallback.callAsync(KrollCallback.java:154) at org.appcelerator.titanium.kroll.KrollCallback.callAsync(KrollCallback.java:89) at org.appcelerator.titanium.kroll.KrollCallback.callAsync(KrollCallback.java:84) at ti.modules.titanium.network.TiHTTPClient.fireCallback(TiHTTPClient.java:468) at ti.modules.titanium.network.TiHTTPClient.fireCallback(TiHTTPClient.java:459) at ti.modules.titanium.network.TiHTTPClient.setReadyState(TiHTTPClient.java:491) at ti.modules.titanium.network.TiHTTPClient$ClientRunnable.run(TiHTTPClient.java:989) at java.lang.Thread.run(Thread.java:1096)</code> </pre></div>{html}

    Appcelerator JIRA | 6 years ago | rGyani
    java.lang.RuntimeException: Handler{43f82b30} sending message to a Handler on a dead thread<br></p> <pre> <code>at android.os.MessageQueue.enqueueMessage(MessageQueue.java:179)
  6. 0

    Exception sending message to a Handler on a dead thread in SycnHttpClient

    GitHub | 3 years ago | ramashishb
    java.lang.RuntimeException: Handler (com.loopj.android.http.AsyncHttpResponseHandler$ResponderHandler) {53554578} sending message to a Handler on a dead thread
Not finding the right solution?
Take a tour to get the most out of Samebug.

Tired of useless tips?

Automated exception search integrated into your IDE

Root Cause Analysis

  1. java.lang.RuntimeException

    Handler{40acfa10} sending message to a Handler on a dead thread

    at android.os.MessageQueue.enqueueMessage()
  2. Android Platform
    Handler.post
    1. android.os.MessageQueue.enqueueMessage(MessageQueue.java:196)
    2. android.os.Handler.sendMessageAtTime(Handler.java:457)
    3. android.os.Handler.sendMessageDelayed(Handler.java:430)
    4. android.os.Handler.post(Handler.java:248)
    4 frames
  3. org.appcelerator.titanium
    KrollCallback.callAsync
    1. org.appcelerator.titanium.kroll.KrollCallback.callAsync(KrollCallback.java:162)
    2. org.appcelerator.titanium.kroll.KrollCallback.callAsync(KrollCallback.java:96)
    3. org.appcelerator.titanium.kroll.KrollCallback.callAsync(KrollCallback.java:91)
    3 frames
  4. ti.modules.titanium
    TiHTTPClient$ClientRunnable.run
    1. ti.modules.titanium.network.TiHTTPClient.fireCallback(TiHTTPClient.java:471)
    2. ti.modules.titanium.network.TiHTTPClient.fireCallback(TiHTTPClient.java:462)
    3. ti.modules.titanium.network.TiHTTPClient.setReadyState(TiHTTPClient.java:494)
    4. ti.modules.titanium.network.TiHTTPClient$ClientRunnable.run(TiHTTPClient.java:1013)
    4 frames
  5. Java RT
    Thread.run
    1. java.lang.Thread.run(Thread.java:1019)
    1 frame