Databases
StackOverflow2013
Postsdbo
POAndroid HttpClient OOM on 4G/LTE (HTC Thunderbolt)
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAndroid HttpClient OOM on 4G/LTE (HTC Thunderbolt)
    primarykey
    data
    text
    <p>I have gotten some reports from users of crashes when try use my application on Verizon's 4G/LTE.</p> <p>Looking at the stack trace, it looks like Android's HttpClient.execute() implementation is throwing an OOM. This happens only on 4G/LTE devices, specifically HTC Thunderbolt, and only when on 4G/LTE. WiFi, 3G, UMTS are OK. Also works fine on Sprint's WiMax 4G stuff works fine.</p> <p>Two questions:</p> <ul> <li><p>What's the best way to get the attention of Android devs about this? Any better options than reporting on <a href="http://code.google.com/p/android/issues">http://code.google.com/p/android/issues</a>?</p></li> <li><p>Any ideas on how I can work around this? I don't have a 4G device myself and I can't get this happen in the emulator so I need to make some educated guesses here. I can try to catch the OOM in my code and attempt to cleanup and force GC, but I'm not sure if that's a good idea. Comments or other suggestions?</p></li> </ul> <p>Here's what my code's doing:</p> <pre><code> HttpParams params = this.getHttpParams(); // returns params ClientConnectionManager cm = new ThreadSafeClientConnManager(params, this.getHttpSchemeRegistry() ); DefaultHttpClient httpClient = new DefaultHttpClient( cm, params ); HttpResponse response = null; request = new HttpGet( url ); try { response = httpClient.execute(request); // &lt;-- OOM on 4G/LTE. OK otherwise int statusCode = response.getStatusLine().getStatusCode(); Log.i("fetcher", "execute returned, http status " + statusCode ); ... </code></pre> <p>Here's the crashing stack trace: </p> <blockquote> <p>E/dalvikvm-heap(11639): Out of memory on a 2055696-byte allocation. I/dalvikvm(11639): "Thread-16" prio=5 tid=9 RUNNABLE I/dalvikvm(11639): | group="main" sCount=0 dsCount=0 s=N obj=0x48563070 self=0x3c4340 I/dalvikvm(11639): | sysTid=11682 nice=0 sched=0/0 cgrp=default handle=3948760 I/dalvikvm(11639): | schedstat=( 208709711 74005130 214 )</p> <p>I/dalvikvm(11639): at org.apache.http.impl.io.AbstractSessionInputBuffer.init(AbstractSessionInputBuffer.java:~79) I/dalvikvm(11639): at org.apache.http.impl.io.SocketInputBuffer.(SocketInputBuffer.java:93) I/dalvikvm(11639): at org.apache.http.impl.SocketHttpClientConnection.createSessionInputBuffer(SocketHttpClientConnection.java:83) I/dalvikvm(11639): at org.apache.http.impl.conn.DefaultClientConnection.createSessionInputBuffer(DefaultClientConnection.java:170) I/dalvikvm(11639): at org.apache.http.impl.SocketHttpClientConnection.bind(SocketHttpClientConnection.java:106) I/dalvikvm(11639): at org.apache.http.impl.conn.DefaultClientConnection.openCompleted(DefaultClientConnection.java:129) I/dalvikvm(11639): at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:173) I/dalvikvm(11639): at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:164) I/dalvikvm(11639): at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:119) I/dalvikvm(11639): at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:348) I/dalvikvm(11639): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:555) I/dalvikvm(11639): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:487) I/dalvikvm(11639): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:465) I/dalvikvm(11639): at com.myapplication.Fetcher.trySourceFetch(Fetcher.java:205) I/dalvikvm(11639): at com.myapplication.Fetcher.run(Fetcher.java:298) I/dalvikvm(11639): at java.lang.Thread.run(Thread.java:1102) I/dalvikvm(11639): E/dalvikvm(11639): Out of memory: Heap Size=24171KB, Allocated=23142KB, Bitmap Size=59KB, Limit=21884KB E/dalvikvm(11639): Extra info: Footprint=24327KB, Allowed Footprint=24519KB, Trimmed=348KB W/dalvikvm(11639): threadid=9: thread exiting with uncaught exception (group=0x40025b38)</p> </blockquote>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USpsychotik
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAndroid HttpClient OOM on 4G/LTE (HTC Thunderbolt)
      1. UScistearns
      1. VTFavorite
    2. VO
      singulars
      1. POAndroid HttpClient OOM on 4G/LTE (HTC Thunderbolt)
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POAndroid HttpClient OOM on 4G/LTE (HTC Thunderbolt)
      1. USEric Nordvik
      1. VTFavorite
    1. COJust confirmation that I'm tracking this same issue. Only appears on htc_mecha (thunderbolt) on verizon_wwe. Issue first appeared March 17 2011.
      singulars
      1. POAndroid HttpClient OOM on 4G/LTE (HTC Thunderbolt)
      1. USDougW
    2. COI went and bought an HTC Thunderbolt to diagnose this issue. What CommonsWare says below is correct. Setting the buffer manually to 8k resolves the crashes. Not sure why HTC decided to change that. Hope they enjoy the phone restocking count++.
      singulars
      1. POAndroid HttpClient OOM on 4G/LTE (HTC Thunderbolt)
      1. USDougW
    3. COAwesome, I was experiencing this problem too. Thanks for the confirmation.
      singulars
      1. POAndroid HttpClient OOM on 4G/LTE (HTC Thunderbolt)
      1. USVictor
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload