diff options
| author | Ari Hausman-Cohen <arihc@google.com> | 2019-02-26 17:11:24 -0800 |
|---|---|---|
| committer | Orion Hodson <oth@google.com> | 2019-04-11 14:17:55 +0100 |
| commit | 9efc7e8782c0e2917095d18c02fdf70461d1a0f0 (patch) | |
| tree | ae40ceefffc2533e9323f37d31964d4059fafdd1 /test/008-exceptions/src/MultiDexBadInitWrapper1.java | |
| parent | dea0153de4aff49c4557ec5f77d3eda6ac1ca41f (diff) | |
Fix tracing shutdown
Method tracing was being disabled before the listener was removed.
In some cases, this would cause the stack restoration to trigger
trace entries - resulting in out-of-order method exits.
By removing the listeners before disabling tracing, no one is around
to receive the erroneous stack restoration "exits".
Bug: 129716777
Test: Builds, ran on x86 emulator:
adb shell am start -S -W --start-profiler \
/data/local/tmp/test.trace --sampling 1 \
-a \android.intent.action.MAIN \
-n com.android.calendar/com.android.calendar.AllInOneActivity && \
sleep 5 && \
adb shell am profile stop com.android.calendar && \
adb pull /data/local/tmp/test.trace
and inspected resulting tracefile; parsed fine in Android Studio 3.0.1
(cherry picked from commit ecd21be250c434d854833aa368610c879fea9245)
Change-Id: I1d14e647eb8801220c78f4487ac4f787806e83d8
Merged-In: I90f0751f4b4253c7c9711d05d53f31b3e545fc3b
Diffstat (limited to 'test/008-exceptions/src/MultiDexBadInitWrapper1.java')
0 files changed, 0 insertions, 0 deletions