tag 269dd57b5ef8cba7709eabb35cca47b6e0018faa
tagger The Android Open Source Project <initial-contribution@android.com> Tue Feb 02 12:46:25 2010 -0800
object ea8eb95a903dda7b277cdbc97523688b9857963b

Android 2.0 release 1

commit ea8eb95a903dda7b277cdbc97523688b9857963b
author Mike Reed <reed@google.com> Thu Oct 01 14:30:06 2009 -0400
committer Mike Reed <reed@google.com> Thu Oct 01 14:30:06 2009 -0400
tree 9d0a847b466f87db5a555d475fb53f6c92625cc4
parent 4b68387a31e4e60a35c6bfd8f532a6b30303e1ff

don't call the inherited saveLayer in record, but just call save.

During record, our clip is wide-open (in the bug's case, 40K pixels tall). If we call saveLayer
with no bounds (as webkit does), we try to allocate an offscreen the size of the document, which
can be arbitrarily big. This cause us to run out of memory. In reality, I think there is not
benefit to calling through to saveLayer during record. On playback, we will of course call saveLayer,
but then we are on a real device (screen) with finite bounds, and the offscreen allocation is
reasonable.