diff options
| author | Hans Boehm <hboehm@google.com> | 2019-04-12 15:28:09 -0700 |
|---|---|---|
| committer | Hans Boehm <hboehm@google.com> | 2019-04-25 17:51:06 -0700 |
| commit | d3a99bc146512720ad63e3f1388f22017c3b98f1 (patch) | |
| tree | 9c9f02c4296305d5dd71964a0219b6071f595f74 /annotations/generate_annotated_java_files.py | |
| parent | bfb34cd493bcf24359d8111efef7ffd01984f45f (diff) | |
Make ArrayDeque clear old array when resizing
ArrayDeques are commonly used for long-lived work queues. If the
queue is resized after the old array has been promoted to the old
GC generation or, in the worst case, has been allocated in a
non-collectable space, everything it referred to remains live
until the old array was collected. This could require a full GC,
or it might never happen.
We now avoid this problem by explicitly clearing the old array
before dropping it.
Bug: 116365212
Bug: 113624968
Bug: 130206915
Test: Boot AOSP, TreeHugger
Merged-In: I614a514180e04440e1d59d69a9b249e5c3db485e
Change-Id: I614a514180e04440e1d59d69a9b249e5c3db485e
(cherry picked from commit 7e1393d1565c76abdd4e667477914cc0562427be)
Diffstat (limited to 'annotations/generate_annotated_java_files.py')
0 files changed, 0 insertions, 0 deletions