diff options
| author | Yohei Yukawa <yukawa@google.com> | 2018-03-20 16:28:59 -0700 |
|---|---|---|
| committer | Yohei Yukawa <yukawa@google.com> | 2018-03-21 01:15:02 +0000 |
| commit | 0cf7b310125ea283f2177d705cb134e895ff32bd (patch) | |
| tree | fdec7dcfa8cde5d7e5cf892bd03259f030ccc123 /rs/java/android/renderscript/Program.java | |
| parent | 3785417848f95c24d2095daeaed0d1cb6b04fb35 (diff) | |
Fix confusing Log.e message in SpellCheckerSession
With this CL, calling SpellCheckerSession#close() multiple times will
no longer show the following error message in logcat, which was quite
confusing.
E SpellCheckerSession: ignoring processOrEnqueueTask due to
unexpected mState=TASK_CLOSE scp.mWhat=TASK_CLOSE
Note that with a recent CL [1], we now more often see the above
message. A typical scenario is:
1. App creates SpellCheckerSession x.
2. App calls x.close().
3. x is garbage-collected. ART calls x.finalize(), which internally
calls x.close() again.
[1]: I4e00c3a2cec93d1dacff20546e481fe757279661
9b64367193ffb252f869fb9f65a60b51a654119e
Bug: 72974646
Fix: 72974646
Test: Made sure that no error message in question with a test app
that calls SpellCheckerSession#close() multiple times then
trigger SpellCheckerSession#finalize().
Change-Id: Ie9690860e6d0406dc6746cd03c28f693e65c1dde
Diffstat (limited to 'rs/java/android/renderscript/Program.java')
0 files changed, 0 insertions, 0 deletions