View details
The details page lists all fault instances that are aggregated for a specific crash. Each instance represents a device on which the fault occurred. The procedure for viewing details is the same for crashes, stuttering, exceptions, and custom reports. This topic uses viewing crash details as an example.
Procedure
Log on to the EMAS console. Find and click your project to navigate to the EMAS Overview page.
In the top navigation bar, select R&D Tools.
In the navigation pane on the left, choose Crash Analysis, and then click Crash, Stuttering, or Exception.
Set the filter conditions as needed and click Query.
In the Crash List, click a crash name to open the aggregation and analysis page for that crash.
Page overview
The left-side navigation pane of the details page lists all fault instances for a specific crash. Click an instance to view its details on the right. The details are organized into tabs, such as Basic Information, Current Options, Crash Stack, Memory Information, Console Log, Custom Data, and Symbol Table.
Page features
The page provides the Resymbolicate and Download features.
Resymbolicate: Re-runs the symbolication process.
Download
Download Log: Downloads the raw log.
Download Stack: Downloads the raw stack.
Basic information
The basic information shows that each instance is a record of a device that experienced this fault.
Parameter |
Description |
Utdid |
The Utdid of the device where the crash occurred. |
AppKey |
The AppKey of the device where the crash occurred. |
App Version |
The app version on the device where the crash occurred. |
User Nickname |
The user nickname on the device where the crash occurred. |
Device Name |
The name of the device where the crash occurred. |
System Version |
The system version on the device where the crash occurred. |
Report Time |
The time when the crash was reported from the device. |
Crash Time |
The time when the crash occurred on the device. |
Startup Time |
The app startup time on the device where the crash occurred. |
Current options
The Current Options tab displays all basic information about this crash.
Parameter |
Description |
appKey |
The AppKey used when integrating Crash Analytics. |
App Version |
The app version passed when integrating Crash Analytics. |
Build Number |
The VersionCode in Android or the BundleVersion in iOS. |
Channel |
The channel ID passed when integrating Crash Analytics. |
Aggregation ID |
The aggregation ID for crashes of the same type. |
Report Time |
The report time. This is the server-side time. |
Startup Time |
The app startup time. This is the client time. |
Crash Time |
The time when the crash occurred. This is the client time. |
Brand |
The brand of the device where the crash occurred. |
Model |
The model ID of the device where the crash occurred. |
Operating System |
The operating system of the device when the crash occurred. |
Version |
The operating system version of the device when the crash occurred. |
Carrier/Network |
The carrier and network information of the device when the crash occurred. |
Country/Region |
The geographical location of the device when the crash occurred, estimated based on the IP address. |
Province/City |
The province and city where the device was located when the crash occurred. |
User IP |
The public IP address of the device when the crash occurred. |
Resolution |
The screen resolution of the device where the crash occurred. |
Page |
The page that was open in the app when the crash occurred. |
Is Foreground |
Indicates whether the crash occurred in a foreground process. |
Is Main Thread |
Indicates whether the crash occurred on the main thread. |
Process Name |
The name of the process that crashed. |
Parent Process Name |
The name of the parent process of the process that crashed. |
CPU Architecture |
The CPU architecture of the device when the crash occurred. |
Language |
The language used by the device when the crash occurred. |
Crash stack
The Crash Stack tab displays the detailed crash stack log that was reported when the crash occurred.
Memory information
The live memory state of the reported sample describes the memory at the time of the crash.
Android
For Android applications, memory information at the time of a crash is retrieved from /proc/meminfo.
Parameter |
Description |
INACTIVE_ANON |
Anonymous memory pages that have not been accessed for a long time. |
VMALLOC_CHUNK |
The largest available contiguous block of virtual memory. |
ACTIVE |
Memory pages that were recently accessed. |
ACTIVE_ANON |
Anonymous memory pages that were recently accessed. |
KERNEL_STACK |
The kernel stack. |
WRITEBACK_TMP |
Temporary buffers used by Filesystem in Userspace (FUSE). |
NFS_UNSTABLE |
Cached pages sent to an NFS server but not yet written to the disk. |
SWAP_FREE |
The amount of free swap space. |
DIRTY |
Cached pages waiting to be written back to the disk. |
VMALLOC_USED |
Virtual memory allocated by vmalloc. |
PAGE_TABLES |
Memory pages used for virtual address mapping. |
SLAB |
Total memory allocated by the slab allocator. |
SWAP_CACHED |
Swap space used by anonymous pages. |
VMALLOC_TOTAL |
Total virtual memory that can be allocated by vmalloc. |
S_UNRECLAIM |
The unreclaimable part of the slab. |
BOUNCE |
Memory used for bounce buffers. |
SWAP_TOTAL |
The total amount of swap space. |
CACHED |
Cached pages occupied by regular files, including those dissociated from processes. |
UNEVICTABLE |
Memory pages that cannot be paged out or swapped out. |
WRITEBACK |
Cached pages that are being written back to the disk. |
MAPPED |
Cached pages occupied by regular files. |
S_RECLAIMABLE |
The reclaimable part of the slab. |
MEM_AVAILABLE |
The available memory estimated by the kernel. |
BUFFERS |
Cached pages occupied by block devices. |
ACTIVE_FILE |
File-backed memory pages that were recently accessed. |
INACTIVE_FILE |
File-backed memory pages that have not been accessed for a long time. |
SHMEM |
Shared memory, including tmpfs and devtmpfs. |
INACTIVE |
Memory pages that have not been accessed for a long time. |
ANON_PAGES |
Anonymous memory pages. |
COMMITTED_AS |
The amount of memory estimated to be needed to complete the current payload. |
MEM_TOTAL |
The total usable memory in the system, excluding memory occupied by the kernel. This value generally remains constant while the system is running. |
MEM_FREE |
The amount of unused memory in the system. |
MLOCKED |
The amount of memory locked by the mlock() system call. |
COMMIT_LIMIT |
The total amount of memory that the system can allocate, calculated based on the overcommit ratio. |
iOS
Parameter |
Description |
active |
The amount of memory currently in active use in the system, in bytes. |
inactive |
The amount of memory currently marked as inactive in the system, in bytes. |
wired |
The amount of memory currently wired down in the system, in bytes. |
free_mem |
The amount of unused memory that can be immediately allocated in the system, in bytes. |
total_mem |
The total amount of physical memory on the device, in bytes. |
virtual |
The total amount of virtual memory currently occupied, in bytes. |
resident |
The actual amount of memory currently residing in physical memory, in bytes. |
footprint |
The total amount of memory that the application actually occupies in physical memory, in bytes. |
HarmonyOS NEXT
Parameter |
Description |
pss |
Proportional Set Size (PSS). The actual physical memory used, proportionally distributed based on the number of references to shared libraries. |
rss |
Resident Set Size (RSS). The actual physical memory used, including memory occupied by shared libraries. |
vss |
Virtual Set Size (VSS). The virtual memory consumed, including memory occupied by shared libraries. |
sys_avail_mem |
The amount of available system memory. |
sys_free_mem |
The amount of free system memory. |
sys_total_mem |
The total amount of system memory. |
Console log
The Console Log tab displays the console data logs that were reported from the device before and after the crash occurred.
Custom data
The Custom Data tab displays custom data that was reported through an SDK callback when the crash occurred. You can view and download the custom logs.
Symbol table
You can upload a symbol table file to the Crash Analytics console. This file is used to deobfuscate the crash call stack, which helps you analyze and resolve the issue.
Symbol tables provide Re-upload and Download options.