Skip to main content

Large Object Analysis

Large objects refer to "bitmap type single objects larger than 1MB" or "other type single objects larger than 256KB".

Filter Conditions​

You can filter data by dimensions such as application version, device, operating system, channel, business scenario, etc.

Large Object List​

  • The large object list displays large object names, average size, object count, affected device count, and version under filter conditions.
  • Large object names support search, you can click πŸ” to search.
  • Large object list data supports export, you can click the button on the right to export

Large Object Details​

After clicking the large object name, you enter the large object details page. The large object details page is displayed in two sections: overview and detailed analysis.

Filter Conditions​

You can filter data by dimensions such as application version, device, operating system, channel, business scenario, etc.

Overview​

Displays object name, object count, affected device count, and you can click the link on the right to share.

Detailed Analysis​

Detailed analysis shows the details of each single sample, including device details and application details.

Device Details: UserID, Launch Time, Occurrence Time, Session Duration, Device ID, Application Version, Device Model, Operating System, SessionID, Region, Carrier, Access Method, Page Name, Business Scenario, CPU Model, CPU Instruction Set, Device Memory, Remaining Memory, Application Memory Usage, Remaining Storage Space, UI Orientation.

Stack Details

Holding Objects (Root Cause Analysis): First check the Retained Heap. If the Retained Heap is particularly large while its own Shallow Heap is relatively small, it indicates that the held objects have not been released in time, and you need to find which large objects in the corresponding class have not released memory, causing GC to be unable to reclaim memory.

  • Object: Formatted as "Object Class Name + Memory Address" or "Object Array + Memory Address".
  • Ref.Objects: Number of objects held, only displaying nodes with Shallow Heap greater than 256KB.
  • Shallow Heap: The size of memory occupied by the object itself.
  • Retained Heap: The sum of all objects that can be removed from memory by GC after the object is collected by the garbage collector. Retained Heap can more accurately reflect the actual memory size occupied by an object.
  • The page supports jumping to Session Details.

Memory Details: Provides memory details data for Android devices, including foreground memory and background memory: physical memory, Java memory usage, video memory, virtual memory, Java memory usage rate, Java physical memory usage, Native physical memory usage.