zezeozue

This commit introduces a significant **UI enhancement** and **refactoring** within the **Heap Dump Explorer**, fundamentally changing how object instances are viewed and navigated. It **replaces the dedicated 'Instances' view** with a more flexible system where **object detail views open as closable tabs**, enabling users to inspect multiple objects side-by-side. Clicking a class in the **Classes tab** now intelligently **filters the Objects tab** by that class name, streamlining the workflow for finding specific instances. This **new capability** also includes updates to the `nav_state.ts` to support the new tab-based navigation and class filtering. Overall, this change provides a **more intuitive and powerful object analysis workflow** for heap dump investigations.

This commit introduces a significant **UI enhancement** to the **Heap Dump Explorer plugin**, specifically for **Flamegraph visualization**. It **refactors** the display mechanism so that opening a Flamegraph from the timeline now renders it as a **standard, closable tab** rather than hijacking the entire view. This change allows users to open and manage **multiple concurrent Flamegraph instances**, greatly improving analysis flexibility within the `heap_dump_page.ts` module. The update also simplifies the underlying rendering logic by removing a special-case path, contributing to better code maintainability and a more consistent user experience.

This commit **fixes a UI bug** in the **HeapDump Explorer** where user-applied `DataGrid` filters were lost when switching between tabs. It resolves this by **removing dynamic `key` props** that forced component remounts and implementing **controlled filter state management** within the `ArraysView`, `BitmapGalleryView`, and `StringsView`. This ensures filters persist across tab switches, significantly improving the user experience by preventing data loss and maintaining context. The change also preserves the ability to apply filters driven by navigation links. Additionally, a new utility function, `clearNavParam`, is introduced in `nav_state.ts` to support navigation parameter handling.

This commit introduces a **new capability** to the **HeapDumpExplorer plugin**, enabling users to visualize dominator tree paths for bitmaps. A new 'Show Paths' toggle in the **bitmap gallery view** allows for batch-fetching and displaying these paths directly within each `BitmapCard`, providing crucial insights into object retention. This feature significantly enhances memory debugging by making it easier to identify GC roots, with trivial paths explicitly marked as "No path to GC root." The change also includes **refactoring** by extracting the `PathEntry` type and exporting reusable functions like `fetchPathFromRoot` and `renderPath` for broader use within the plugin's UI components.

This commit introduces a **user interface enhancement** to the **Heap Dump Explorer plugin**, specifically within the `ObjectView` component. It modifies the display logic for several sections, including 'Sample Path from GC Root', 'Fields', 'Objects with References', and 'Immediately Dominated Objects'. Instead of completely hiding these sections when no data is present, the `ObjectView` will now render informative empty state messages. This **improves user experience** by providing clearer feedback and preventing confusion when certain object details are absent.

This commit introduces significant **enhancements to the HeapDump Explorer UI**, primarily by adding **duplicate primitive array detection** and a new **Arrays tab**. It allows users to identify redundant primitive arrays directly in the overview, and then navigate to the dedicated `ArraysView` to inspect all primitive array objects, filterable by content hash. Furthermore, this update **improves existing memory analysis capabilities** by removing the `LIMIT 100` cap on duplicate strings and fixing `DataGrid` height for proper virtual scrolling in overview sections, providing a more comprehensive and performant user experience for memory leak investigation.

This commit introduces a **new capability** to enhance **Java heap analysis** by integrating the **HeapProfile flamegraph** with the **Heapdump Explorer**. Users can now select a node in the Java flamegraph and use the new "Open in Heapdump Explorer" action to navigate to a dedicated view (`FlamegraphObjectsView`) within the `HeapDumpExplorer` that displays the individual heap objects corresponding to that flamegraph path. This **improves cross-tool navigation and detailed object inspection**, while also **refactoring** the `HeapProfile` plugin to remove less-used reference viewing actions and **fixing a query bug** in `HeapDumpExplorer` related to `NULL field_type_name` values.

This commit introduces a **new CI workflow** for the **`bigtrace` UI**, automating its build and deployment to GCS whenever files under `ui/src/bigtrace/` are modified. The new `.github/workflows/bigtrace-tests.yml` workflow posts a link to the built `bigtrace.html` on pull requests, with its failures configured as non-blocking to avoid disrupting other development. This **new capability** also **fixes an existing build issue** with `ui/build --bigtrace` and **refactors** the `bigtrace` UI initialization in `ui/src/bigtrace/index.ts` for improved structure. Overall, this **maintenance** and **refactoring** effort significantly streamlines the development and testing process for the `bigtrace` UI by enhancing the **CI/CD infrastructure**.

This commit introduces a **new capability** by adding the **Heapdump Explorer plugin** (`com.android.HeapDumpExplorer`) to the **UI**. Inspired by Android's ahat tool, this plugin provides comprehensive heap analysis through various views, including an overview dashboard, classes, objects, instances, dominators, a bitmap gallery, and strings. It leverages `DataGrid` with `SQLDataSource` for efficient sorting and filtering of large datasets, significantly enhancing the project's ability to analyze memory usage. This feature impacts the **UI's debugging and profiling tools**, offering detailed insights into heap dumps.

This commit significantly **enhances the ART HPROF heap dump analysis** capabilities within the **trace processor** by introducing **new support for primitive fields and array contents**. It adds `heap_graph_object_data` and `heap_graph_primitive` tables to store this detailed information, with the `art_hprof_parser` and `art_heap_graph_resolver` updated to extract and decode these values, including Java strings. To facilitate querying, **new SQL intrinsic functions** like `HeapGraphArray` and `HeapGraphArrayJson` are provided, allowing users to retrieve primitive array data as raw bytes or JSON. This **new capability** also incorporates `array_data_hash` for content deduplication, particularly for bitmaps, ultimately offering much richer and more granular data for memory analysis.

This commit provides a **fix** to achieve **ahat parity** for the **HPROF importer** within **Trace Processor**, ensuring consistent heap analysis data. It precisely aligns the computation of `self_size`, `native_size`, `reachability`, `root_type`, and qualified field names with `ahat`'s behavior. This involves significant updates across the **ART HPROF import pipeline**, including implementing **root type precedence**, shortest-path root distance calculation, and correctly skipping "referent" fields for classified reference types during reachability analysis. Consequently, the raw table output generated by Trace Processor for `.hprof` files will now be **identical to `ahat`**, improving data reliability for memory profiling. This work primarily affects the `art_heap_graph_builder`, `art_heap_graph_resolver`, and `art_hprof_parser` components.

This commit performs **maintenance refactoring** within the **Android trace event SDK** by updating the `android_track_event.proto` schema. Specifically, it **renames enum values** in `ReceiverType`, `AppExitReasonCode`, `AppExitSubReasonCode`, `Importance`, and `OomChangeReasonEnum` to align with standard protobuf naming patterns. This ensures **consistency and adherence to best practices** for the protobuf definitions, improving the overall **code quality** and maintainability of the trace event schema. The change primarily affects internal schema definitions, with a positive impact on downstream tools consuming these standardized trace events.

This commit introduces a **new capability** to the **Perfetto SDK** by enhancing **Android process state tracking** with detailed **CPU time reasons**. Specifically, it adds `cpu_time_reasons` and `implicit_cpu_time_reasons` fields to the `AndroidProcessStateChangedEvent`, providing more granular insights into CPU usage during process state transitions for improved **performance analysis**. Additionally, it **refactors** the `capability flags` field to `int32` for better bitmask handling and extends the `TraceConfig` with a new `notes` field, allowing arbitrary key-value metadata to be attached to trace configurations.

This commit introduces a **new capability** to the **Perfetto SDK** by adding an `AndroidBinderDiedEvent` to the **Android tracing events**. This event provides early notification of binder process deaths, addressing delays encountered with `AppExitInfoTracker`. By logging these events promptly without detailed death reasons, it significantly **simplifies downstream analysis** and improves PID tracking for Android system performance investigations. The change involves defining the new `AndroidBinderDiedEvent` proto message and integrating it as an extension to `TrackEvent` within `protos/perfetto/trace/android/android_track_event.proto`.

This commit introduces a **new feature** in the **Perfetto Android SDK** by modifying the `expensiveDebugCallStack` method within `PerfettoTrace.java`. The method now returns a `PerfettoTrackEventBuilder`, enabling callers to **chain additional event protos** such as explicit tracks directly onto the callstack event. This enhancement significantly improves the API's flexibility and streamlines the process of augmenting trace events. The change also aligns the behavior of callstack events with other event types like counter or instant, where further modifications are expected before final emission.

This commit introduces an **enhancement** to the **Perfetto Android SDK**, specifically within the `PerfettoTrace` class. The `emitExpensiveDebugCallStack` method has been modified to accept a pre-generated `StackTraceElement[]` argument, removing its internal stack trace generation logic. This change allows callers to pass cached stack traces, thereby **improving performance** by offloading the potentially expensive stack trace dumping from the SDK itself. The update provides greater flexibility for integrating Perfetto tracing with existing stack trace mechanisms.

This commit introduces a **new capability** by adding a `seq_id` field to the `AndroidProcessStateChangedEvent` within the **Android tracing protobuf schema**. This enhancement allows for more precise tracking and ordering of **Android process state changes**, improving the fidelity of process lifecycle analysis. The change affects both the `protos/perfetto/trace/android/android_track_event.proto` definition and its corresponding generated C++ header, `include/perfetto/public/protos/trace/android/android_track_event.pzc.h`. This update provides a critical identifier for consumers of these events to understand the sequence of state transitions.

This commit introduces a **new debugging capability** to the **Perfetto SDK** by adding a utility to capture and emit Java stack traces directly into a Perfetto trace. The `PerfettoTrace.java` module now includes the `emitExpensiveDebugCallStack` method, which facilitates **local debugging** by providing detailed call flow insights. This **feature** is specifically designed for diagnostic use and is noted as expensive due to its underlying `Thread.getStackTrace()` operation. Consequently, it **must not be used in production hot paths** to avoid performance degradation.

This commit **refactors** the **Android tracing SDK** by replacing generic `uint32` types with explicit **enum types** for **Android lifecycle and broadcast events**. This **semantic improvement** allows the **Perfetto UI** to display these events as human-readable strings, greatly enhancing **trace data readability** and simplifying **analysis**. The changes primarily affect the `protos/perfetto/trace/android/android_track_event.proto` definition and its generated C++ headers, improving **maintainability** and consistency by aligning with `statsd` atom enums.

This commit introduces **new Android process lifecycle and broadcast track events** to the Perfetto SDK, significantly enhancing its ability to monitor Android application behavior. It captures critical events like process starts, deaths, state changes, broadcast deliveries, and freezer transitions, providing data equivalent to low-level kernel events for managed Java processes. By including process names, it aids the `TraceProcessor` in detecting PID reuse without ftrace overhead. This **new capability** extends the `AndroidTrackEvent` protobuf and related tracing configurations, enabling deeper insights into Android system and app performance.