Strict Mode exception regarding a FileInputStream isn't closed

256 views
Skip to first unread message

Quinn Neumiiller

unread,
Sep 29, 2014, 6:17:04 PM9/29/14
to google-adm...@googlegroups.com
We're getting the following StrictMode exception regarding a FileInputStream that isn't being closed properly:

09-29 15:09:10.463: E/StrictMode(3593): A resource was acquired at attached stack trace but never released. See java.io.Closeable for information on avoiding resource leaks.
09-29 15:09:10.463: E/StrictMode(3593): java.lang.Throwable: Explicit termination method 'close' not called
09-29 15:09:10.463: E/StrictMode(3593): at dalvik.system.CloseGuard.open(CloseGuard.java:184)
09-29 15:09:10.463: E/StrictMode(3593): at java.io.FileInputStream.<init>(FileInputStream.java:80)
09-29 15:09:10.463: E/StrictMode(3593): at com.google.android.ads.zxxz.d.b(Unknown Source)
09-29 15:09:10.463: E/StrictMode(3593): at com.google.android.ads.zxxz.d.a(Unknown Source)
09-29 15:09:10.463: E/StrictMode(3593): at java.lang.reflect.Method.invokeNative(Native Method)
09-29 15:09:10.463: E/StrictMode(3593): at java.lang.reflect.Method.invoke(Method.java:515)
09-29 15:09:10.463: E/StrictMode(3593): at com.google.android.a.r.a(SourceFile:316)
09-29 15:09:10.463: E/StrictMode(3593): at com.google.android.a.r.b(SourceFile:159)
09-29 15:09:10.463: E/StrictMode(3593): at com.google.android.a.t.b(SourceFile:120)
09-29 15:09:10.463: E/StrictMode(3593): at com.google.android.a.q.a(SourceFile:258)
09-29 15:09:10.463: E/StrictMode(3593): at com.google.android.a.q.a(SourceFile:195)
09-29 15:09:10.463: E/StrictMode(3593): at com.google.android.gms.ads.internal.k.a(SourceFile:76)
09-29 15:09:10.463: E/StrictMode(3593): at com.google.android.gms.ads.internal.request.c.f_(SourceFile:99)
09-29 15:09:10.463: E/StrictMode(3593): at com.google.android.gms.ads.internal.util.b.run(SourceFile:17)
09-29 15:09:10.463: E/StrictMode(3593): at com.google.android.gms.ads.internal.util.d.call(SourceFile:29)
09-29 15:09:10.463: E/StrictMode(3593): at com.google.android.gms.ads.internal.util.e.call(SourceFile:49)
09-29 15:09:10.463: E/StrictMode(3593): at java.util.concurrent.FutureTask.run(FutureTask.java:237)
09-29 15:09:10.463: E/StrictMode(3593): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
09-29 15:09:10.463: E/StrictMode(3593): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
09-29 15:09:10.463: E/StrictMode(3593): at java.lang.Thread.run(Thread.java:841)


Eric Leichtenschlag

unread,
Sep 29, 2014, 9:51:05 PM9/29/14
to google-adm...@googlegroups.com
Thanks for reporting. I've filed a bug for this.

Eric Leichtenschlag

unread,
Oct 3, 2014, 11:42:51 AM10/3/14
to google-adm...@googlegroups.com
There will be a fix for this in the next major release after Google Play services 6.1.

Quinn Neumiiller

unread,
Oct 3, 2014, 11:43:31 AM10/3/14
to google-adm...@googlegroups.com
Awesome! Thanks Eric.

--

---
You received this message because you are subscribed to a topic in the Google Groups "Google AdMob Ads Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/FWX2Jb0XNnc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

kenneth rankin

unread,
Oct 29, 2014, 1:41:27 PM10/29/14
to google-adm...@googlegroups.com
Any idea when this will be fixed or do I have something wrong somewhere in my code?

kenneth rankin

unread,
Oct 29, 2014, 1:47:11 PM10/29/14
to google-adm...@googlegroups.com
Are you using multidex by any chance?


On Monday, September 29, 2014 5:17:04 PM UTC-5, Quinn Neumiiller wrote:

Eric Leichtenschlag

unread,
Oct 30, 2014, 10:23:09 AM10/30/14
to google-adm...@googlegroups.com
Hey guys,

Just an update that this will actually not be included in the next release, but in the following release after that, expected in Q1 2015. Sorry for the delay on this, but hopefully it isn't a big deal since it's just a strict mode warning.

Thanks,
Eric
Reply all
Reply to author
Forward
0 new messages