Quantcast
Channel: Appcelerator Developer Center Q&A Unanswered Questions 20
Viewing all articles
Browse latest Browse all 8068

Android Titanium app crashing without much more than Fatal signal, maybe related to HTTP client exception

$
0
0

Hi,

I load an image via HTTP from a server into the app. Sometimes the client seems to be unable to find the image at the url I supply. This is not bad, the image just does not get displayed. What is bad is that somtimes the app just closes without a stack trace, I don't know though if it is connected to the 'not found' error (logs are from Android Device Monitor, I am using Titanium SDK version 3.2.1.GA):

06-12 19:13:36.348: E/TiHttpClient(24381): (TiHttpClient-72) [609,391139] HTTP Error (org.apache.http.client.HttpResponseException): Not Found
06-12 19:13:36.348: E/TiHttpClient(24381): org.apache.http.client.HttpResponseException: Not Found
06-12 19:13:36.348: E/TiHttpClient(24381):  at ti.modules.titanium.network.TiHTTPClient$LocalResponseHandler.handleResponse(TiHTTPClient.java:258)
06-12 19:13:36.348: E/TiHttpClient(24381):  at ti.modules.titanium.network.TiHTTPClient$LocalResponseHandler.handleResponse(TiHTTPClient.java:217)
06-12 19:13:36.348: E/TiHttpClient(24381):  at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:657)
06-12 19:13:36.348: E/TiHttpClient(24381):  at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:637)
06-12 19:13:36.348: E/TiHttpClient(24381):  at ti.modules.titanium.network.TiHTTPClient$ClientRunnable.run(TiHTTPClient.java:1287)
06-12 19:13:36.348: E/TiHttpClient(24381):  at java.lang.Thread.run(Thread.java:841)
06-12 19:13:36.688: A/libc(24381): Fatal signal 11 (SIGSEGV) at 0x0000000c (code=1), thread 24396 (KrollRuntimeThr)
So my question is: should the 'not found' exception crash the app? I was under the impression it just gracefully let's the app continue. If it indeed maye crash the app, how do I handle this? The client just can't find the image.

If there might be another cause for the crash: how do I go about finding the root of this provlem if there is no stack trace but just this:

06-12 19:13:36.688: A/libc(24381): Fatal signal 11 (SIGSEGV) at 0x0000000c (code=1), thread 24396 (KrollRuntimeThr)

Viewing all articles
Browse latest Browse all 8068

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>