Fix dump_at_max bookkeeping bug.
The object count was incorrect.
Bug: 179485777
Change-Id: I628c5ef8987799fbecc9d87c580b1fa61cff7dc7
diff --git a/docs/data-sources/native-heap-profiler.md b/docs/data-sources/native-heap-profiler.md
index 486af16..05dd4bb 100644
--- a/docs/data-sources/native-heap-profiler.md
+++ b/docs/data-sources/native-heap-profiler.md
@@ -458,6 +458,7 @@
resolved in Android 12.
* `Failed to send control socket byte.` is displayed in logcat at the end of
every profile. This is benign.
+* The object count may be incorrect in `dump_at_max` profiles.
### {#known-issues-android10} Android 10
* Function names in libraries with load bias might be incorrect. Use
@@ -482,6 +483,7 @@
This is an invalid config that should be rejected instead.
* `Failed to send control socket byte.` is displayed in logcat at the end of
every profile. This is benign.
+* The object count may be incorrect in `dump_at_max` profiles.
## Heapprofd vs malloc_info() vs RSS
