summaryrefslogtreecommitdiff
path: root/compiler/optimizing/optimizing_compiler_stats.h
diff options
context:
space:
mode:
author Ioannis Ilkos <ilkos@google.com> 2024-10-17 19:29:23 +0000
committer Treehugger Robot <android-test-infra-autosubmit@system.gserviceaccount.com> 2024-11-11 13:47:13 +0000
commit5656cd41481ab03eb6df3aec7eda296ebbef667b (patch)
tree2fdb8b5e96cc50fb26643a9e00df6a7d0f7bb490 /compiler/optimizing/optimizing_compiler_stats.h
parent939772b8f0548655e598f68f5af442f512236138 (diff)
Reduce the likelihood of the child process being stuck
The design of the hprof plugin prioritizes minimizing the impact of the process being dumped, and does so by forking (inherently unreliable) Besides suspending all threads (already the case) there are additional tweaks we can do to reduce the chance of being stuck in a fork-unfriendly code path: - Stop using LOG in the child process (at least until the heap dump has been completed) - Optimistically get the thread_list_lock_ to avoid forking at an unfortunate time These were both discovered by running the CTS tests repeatedly and looking for flakes. Change-Id: I4934e920c1eb57aca339b7b220c63e9650c00c7e Bug: 376421756 Test: atest CtsPerfettoTestCases:HeapprofdJavaCtsTest
Diffstat (limited to 'compiler/optimizing/optimizing_compiler_stats.h')
0 files changed, 0 insertions, 0 deletions