| commit | 2aa911c01e940383dca0b1afbf58a3439aaa748a | [log] [tgz] |
|---|---|---|
| author | Hans Boehm <hboehm@google.com> | Fri Oct 12 17:16:27 2018 -0700 |
| committer | Hans Boehm <hboehm@google.com> | Fri Oct 19 18:35:29 2018 -0700 |
| tree | 60b6726c142cde4e8050b76dd77613cc2de9947d | |
| parent | 6622d0957d0ab01f9808901ccf5d9e2e440ea5e1 [diff] |
Remove NotificationVisibility storage pool Based on recent measurements, storage pools of small objects are generally not useful. We ran into this because growing ArrayDeques are potentially very unfriendly towards a generational GC, and racing recycle calls can cause it it grow beyond MAX_POOL_SIZE. This isn't a big deal, but there's no reason we should even be thinking about it. Test: Build and boot AOSP Change-Id: Icbda95e472e206c54f141129cc36ddc6d163b095