diff options
| author | 2022-10-26 09:44:06 +0000 | |
|---|---|---|
| committer | 2022-11-01 10:56:29 +0000 | |
| commit | 1285ef99ae82a1972330ca9337b12db3eb573bbe (patch) | |
| tree | 6c59af6e251d2938f41a353648213872b4cf6b2c /compiler/optimizing/optimizing_compiler_stats.h | |
| parent | f2a1e0f65ade47b9ee7c315d16e54a50b765b85e (diff) | |
Don't update listeners / instrumentation levels when shutting down
When a plugin is unloaded, JVMTI unregisters listeners and updates
instrumentation level to remove any instrumentation added for jvmti.
However when we unload the plugin as a part of runtime shutdown it
is not always safe to update instrumentation level or update runtime
callbacks. Several of these require a GC critical section and a suspend
all scope. When we are unloading a plugin due to a shutdown GC has
already stopped and requesting a GC critical section is unsafe. So this
CL just returns early if we are unloading the plugin as a part of the
shutdown.
Test: art/test.py
Change-Id: Ieb4d57926ab007776e9110da5f3fd4ae518186d4
Diffstat (limited to 'compiler/optimizing/optimizing_compiler_stats.h')
0 files changed, 0 insertions, 0 deletions