java_hprof: Regenerate the list of pids on continuous dump.
With this change, by default, the java heap profiler will rescan all the
processes every time when operating in continuous dump mode.
This is useful to collect data on processes that are not yet started
when tracing starts.
Tests:
* Regression: take a single java heap dump with a process name
`./tools/java_heap_dump -n com.android.messaging`
* Regression: take a single java heap dump with a pid
`./tools/java_heap_dump -p 3998`
* Regression: take a continuous java heap dump with an existing process
name
`./tools/java_heap_dump -n com.android.messaging -c 2000 --no-stop-when-done`
* Regression: take a continuous java heap dump with an existing pid
`./tools/java_heap_dump -p 3998 -c 2000 --no-stop-when-done`
* New behavior: take a continuous java heap dump with the name of a
process that gets started later.
* `adb shell killall com.android.messaging`
* `./tools/java_heap_dump -c com.android.messaging -c 2000 --no-stop-when-done`
* Wait a bit
* Start the messaging app
Bug: 200534390
Change-Id: I89bac451d6803b73009ad669bff31fbb487b9d58
diff --git a/CHANGELOG b/CHANGELOG
index e316684..3bf07a9 100644
--- a/CHANGELOG
+++ b/CHANGELOG
@@ -4,6 +4,9 @@
* Changed compiler flags. Assume recent x64 CPUs (-msse4.2 -mavx -mpopcnt).
This behavior affects only standalone builds and can be changed by setting
enable_perfetto_x64_cpu_opt=false in the GN args.
+ * The java heap profiler now rescans all the processes every time for
+ continous_dump_config. The scan_pids_only_on_start can be used to restore
+ the old behavior.
Trace Processor:
* Changed LIKE comparisions to be case-senstive. This may break existing
queries but was a necessary from a performance perspective.