| commit | 191cdf023c3c1ab441087a77f7881c7bb376613a | [log] [tgz] |
|---|---|---|
| author | Brad Fitzpatrick <bradfitz@android.com> | Mon Oct 11 11:31:15 2010 -0700 |
| committer | Brad Fitzpatrick <bradfitz@android.com> | Mon Oct 11 11:31:15 2010 -0700 |
| tree | cd3eb3d5abdf7eef5ac1dcd6728fbf61c994b806 | |
| parent | 4e1658afb8a79aa03a5ca712b02b2a33fb00bf6d [diff] |
StrictMode: check max-offenses-per-loop earlier, before allocations Previously a tight loop of StrictMode violations would still allocate Exception objects and populate their stack frames, just to orphan them later when checking the max-10-violations-per-loop constraint. With this patch, we do that check _before_ allocating any memory. Change-Id: Iae96aba33f8fcc6a8ec5838a231aecc08e95122d