diff options
| author | Christopher Tate <ctate@google.com> | 2011-08-23 15:47:46 -0700 |
|---|---|---|
| committer | Christopher Tate <ctate@google.com> | 2011-08-23 16:26:57 -0700 |
| commit | 2611f89ab4f1119b96123edb2cd6d8d8139c03c4 (patch) | |
| tree | 847f480e0f8f1e603ba413f7dc1b936208c1c11e /docs/html/sdk/api_diff/14/changes | |
| parent | e20c279d9a6719a7c0d8c6606c7ba1bd207db8d3 (diff) | |
Warn only if we're tearing down "live" DeathRecipient content
If the native-side bookkeeping still has strong references to VM-side
DeathRecipient objects at the time when it's being torn down, that
suggests that the app is doing unwholesome. Log a warning to that
effect, with the class name of the objects to try to help the developer
figure out what they're mishandling.
Fixes bug 5202777 -- in particular, it no longer logs in the
working-as-intended case following delivery of the death notices,
when we've got the existing list shell but the weak refs have properly
cleared. Also step down from "error" to "warning" logging as befits
the nature of the actual situation now being described.
Change-Id: Ic393560824800fbd912a6e69692c65be4fcc7544
Diffstat (limited to 'docs/html/sdk/api_diff/14/changes')
0 files changed, 0 insertions, 0 deletions