An awfully big String - in Admob Android SDK 4.1.0

[William Ferguson]

I've only seen one instance of this, but something in the Admob SDK
(b#a) is trying to create an awfully big String.

--------------
java.lang.RuntimeException: An error occured while executing
doInBackground()
at android.os.AsyncTask$3.done(AsyncTask.java:200)
at java.util.concurrent.FutureTask
$Sync.innerSetException(FutureTask.java:273)
at java.util.concurrent.FutureTask.setException(FutureTask.java:124)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:307)
at java.util.concurrent.FutureTask.run(FutureTask.java:137)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:
1068)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:561)
at java.lang.Thread.run(Thread.java:1096)
Caused by: java.lang.OutOfMemoryError: array size too large
at
java.lang.AbstractStringBuilder.enlargeBuffer(AbstractStringBuilder.java:
97)
at java.lang.AbstractStringBuilder.append0(AbstractStringBuilder.java:
157)
at java.lang.StringBuilder.append(StringBuilder.java:217)
at b.a(Unknown Source)
at b.doInBackground(Unknown Source)
at android.os.AsyncTask$2.call(AsyncTask.java:185)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:305)
... 4 more
java.lang.OutOfMemoryError: array size too large
at
java.lang.AbstractStringBuilder.enlargeBuffer(AbstractStringBuilder.java:
97)
at java.lang.AbstractStringBuilder.append0(AbstractStringBuilder.java:
157)
at java.lang.StringBuilder.append(StringBuilder.java:217)
at b.a(Unknown Source)
at b.doInBackground(Unknown Source)
at android.os.AsyncTask$2.call(AsyncTask.java:185)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:305)
at java.util.concurrent.FutureTask.run(FutureTask.java:137)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:
1068)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:561)
at java.lang.Thread.run(Thread.java:1096)
--------------

[Tim]

William,

Thanks for the stack trace. We'll keep an eye out for that. I'm pretty
sure that this stack trace means that the phone ran out of memory
while trying to store the HTML for the ad. Let us know if you see any
more reports of that error.

Thanks,
-Tim



On Jun 23, 6:38 am, William Ferguson <william.ferguson...@gmail.com>
wrote: