Thank you for your reply,
1) We haven't been able to reproduce the crash on our end.
The crash has been reported through a crash reporting service (Crashlytics/Fabric), during the last week there were ~1000 crashes reported.
The affect devices range from a multitude of brands and models (e.g.: Samsung, Sony, HTC, ...). One device that has seen most of the crashes is
Samsung SM-G900F (S5).2) As far as I know, currently I have no way of knowing this
3) Android SDK: 5.1 (API 22), we support API 16+,
Google Mobile Ads SDK: I actually don't know the exact version, it is setup to always use the newer version available.
The apps were built and compiled on the 22nd of April, so I guess it used the version that was available at that time.
4) That is the only stacktrace that I have. I was able to "pinpoint" the problem using the breadcrumbs report and the Google Analytics error reports.
On Google Analytics the crash only appears associated with the AdActivity and on the breadcrumbs it happens after the call to "showFullScreenAd" which shows an Interstitial Ad.
Another thing is that the crashes seem to happen more frequently with our german users than with the others, which makes me wonder if it is a problem related with a specific group of ads.
Searching for the problem, the more info I could get was on stackoverflow (
http://stackoverflow.com/questions/27232275/java-util-concurrent-timeoutexception-android-view-threadedrenderer-finalize), but that is related to WebViews which we don't use on our app.