There's one crash after the fix of bug 802510: bp-57931e31-9713-438b-810b-237d52121117. java.lang.RuntimeException: Buffer not large enough for pixels at android.graphics.Bitmap.copyPixelsFromBuffer(Bitmap.java:673) at org.mozilla.gecko.GeckoApp.handleThumbnailData(GeckoApp.java:733) at org.mozilla.gecko.ScreenshotHandler$2.run(ScreenshotHandler.java:370) at android.os.Handler.handleCallback(Handler.java:608) at android.os.Handler.dispatchMessage(Handler.java:92) at android.os.Looper.loop(Looper.java:156) at org.mozilla.gecko.util.GeckoBackgroundThread.run(GeckoBackgroundThread.java:31) More reports at: https://crash-stats.mozilla.com/report/list?signature=java.lang.RuntimeException%3A+Buffer+not+large+enough+for+pixels+at+android.graphics.Bitmap.copyPixelsFromBuffer%28Bitmap.java%29
It's #2 top crasher in 19.0a2 and #11 in 20.0a1.
tracking-fennec: --- → ?
status-firefox19: --- → affected
status-firefox20: --- → affected
tracking-firefox19: --- → ?
Assignee: nobody → bugmail.mozilla
tracking-fennec: ? → 19+
6 years ago
Depends on: 817067
I posted STR (requires a code change to widen the race condition window) to bug 817067.
If I'm reading the stats right, this hasn't happened on nightly since 817067 landed, which is promising. Will leave open a few more days to confirm.
Build ID 2012120303 is the last one on 20.0a1 I'm seeing this is, before this we have been seeing this in builds from almost every day. 1) I think we can mark this bug fixed, 2) how risky is the patch in bug 817067 to be uplifted to 19 or even 18?
Uplifting to 19 should be easy and safe enough. Uplifting to 18 is much harder because that patch assumes patches from bug 787765 are applied, and those are only in 19. However I don't think the crash volume on 18 for this bug is that high anyway (it was aggravated by bug 787765 in 19+) so we shouldn't need to uplift to 18 anyway.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
status-firefox20: affected → fixed
Target Milestone: --- → Firefox 20
The patch of bug 817067 landed in Aurora.
status-firefox19: affected → fixed
You need to log in before you can comment on or make changes to this bug.