@ohos.hidebug (HiDebug)

This module provides multiple methods for debugging and profiling applications. With these methods, you can obtain memory, CPU, GPU, and GC data, collect process trace and profiler data, and dump VM heap snapshots. Since most APIs of this module are both performance-consuming and time-consuming, and are defined based on the HiDebug module, you are advised to use these APIs only during the application debugging and profiling phases. If the APIs are required in other scenarios, evaluate the impact of the APIs on application performance.

NOTE

The initial APIs of this module are supported since API version 8. Newly added APIs will be marked with a superscript to indicate their earliest API version.

Modules to Import

import { hidebug } from '@kit.PerformanceAnalysisKit';

hidebug.getNativeHeapSize

getNativeHeapSize(): bigint

Obtains the total number of bytes occupied by the total space (uordblks + fordblks, which are obtained from mallinfo) held by a process, which is measured by the memory allocator.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Return value

Type	Description
bigint	Size of the memory occupied by the total space held by the process, in bytes.

Example

import { hidebug } from '@kit.PerformanceAnalysisKit';

let nativeHeapSize: bigint = hidebug.getNativeHeapSize();

hidebug.getNativeHeapAllocatedSize

getNativeHeapAllocatedSize(): bigint

Obtains the total number of bytes occupied by the total allocated space (uordblks, which is obtained from mallinfo) held by a process, which is measured by the memory allocator.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Return value

Type	Description
bigint	Size of the memory occupied by the total allocated space held by the process, in bytes.

Example

import { hidebug } from '@kit.PerformanceAnalysisKit';

let nativeHeapAllocatedSize: bigint = hidebug.getNativeHeapAllocatedSize();

hidebug.getNativeHeapFreeSize

getNativeHeapFreeSize(): bigint

Obtains the total number of bytes occupied by the total free space (fordblks, which is obtained from mallinfo) held by a process, which is measured by the memory allocator.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Return value

Type	Description
bigint	Size of the memory occupied by the total free space held by the process, in bytes.

Example

import { hidebug } from '@kit.PerformanceAnalysisKit';

let nativeHeapFreeSize: bigint = hidebug.getNativeHeapFreeSize();

hidebug.getPss

getPss(): bigint

Obtains the size of the physical memory actually used by the application process. This API is implemented by summing up the values of Pss and SwapPss in the /proc/{pid}/smaps_rollup node.

NOTE

Reading the /proc/{pid}/smaps_rollup node is time-consuming. Therefore, you are advised not to use this API in the main thread. You can use this API in the asynchronous thread started by calling @ohos.taskpool or @ohos.worker to avoid frame freezing.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Return value

Type	Description
bigint	Size of the physical memory actually used by the application process, in KB.

Example

import { hidebug } from '@kit.PerformanceAnalysisKit';

let pss: bigint = hidebug.getPss();

hidebug.getVss¹¹⁺

getVss(): bigint

Obtains the virtual set size used by the application process. This API is implemented by multiplying the value of size (number of memory pages) in the /proc/{pid}/statm node by the page size (4 KB per page).

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Return value

Type	Description
bigint	Virtual set size used by the application process, in KB.

Example

import { hidebug } from '@kit.PerformanceAnalysisKit';

let vss: bigint = hidebug.getVss();

hidebug.getSharedDirty

getSharedDirty(): bigint

Obtains the size of the shared dirty memory of a process. This API is implemented by reading the value of Shared_Dirty in the /proc/{pid}/smaps_rollup node.

NOTE

Reading the /proc/{pid}/smaps_rollup node is time-consuming. Therefore, you are advised not to use this API in the main thread. You can use this API in the asynchronous thread started by calling @ohos.taskpool or @ohos.worker to avoid frame freezing.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Return value

Type	Description
bigint	Size of the shared dirty memory of the process, in KB.

Example

import { hidebug } from '@kit.PerformanceAnalysisKit';

let sharedDirty: bigint = hidebug.getSharedDirty();

hidebug.getPrivateDirty⁹⁺

getPrivateDirty(): bigint

Obtains the size of the private dirty memory of a process. This API is implemented by reading the value of Private_Dirty in the /proc/{pid}/smaps_rollup node.

NOTE

Reading the /proc/{pid}/smaps_rollup node is time-consuming. Therefore, you are advised not to use this API in the main thread. You can use this API in the asynchronous thread started by calling @ohos.taskpool or @ohos.worker to avoid frame freezing.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Return value

Type	Description
bigint	Size of the private dirty memory of the process, in KB.

Example

import { hidebug } from '@kit.PerformanceAnalysisKit';

let privateDirty: bigint = hidebug.getPrivateDirty();

hidebug.getCpuUsage⁹⁺

getCpuUsage(): number

Obtains the CPU usage of a process.

For example, if the CPU usage is 50%, 0.5 is returned.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Return value

Type	Description
number	CPU usage of the process.

Example

import { hidebug } from '@kit.PerformanceAnalysisKit';

let cpuUsage: number = hidebug.getCpuUsage();

hidebug.getServiceDump⁹⁺

getServiceDump(serviceid: number, fd: number, args: Array<string>) : void

Obtains system service information.

Required permissions: ohos.permission.DUMP (available only for system applications)

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Parameters

Name	Type	Mandatory	Description
serviceid	number	Yes	Obtains the system service information based on the specified service ID.
fd	number	Yes	File descriptor to which data is written by the API.
args	Array<string>	Yes	Parameter list of the Dump API of the system service.

Error codes

For details about the error codes, see HiDebug Error Codes.

ID	Error Message
401	the parameter check failed,Possible causes:1.the parameter type error 2.the args parameter is not string array.
11400101	ServiceId invalid. The system ability does not exist.

Example

import { fileIo } from '@kit.CoreFileKit';
import { hidebug } from '@kit.PerformanceAnalysisKit';
import { BusinessError } from '@kit.BasicServicesKit';

let fileFd = -1;
try {
  let path: string = this.getUIContext().getHostContext()!.filesDir + "/serviceInfo.txt";
  console.info("output path: " + path);
  fileFd = fileIo.openSync(path, fileIo.OpenMode.READ_WRITE|fileIo.OpenMode.CREATE).fd;
  let serviceId: number = 10;
  let args: Array<string> = new Array("allInfo");
  hidebug.getServiceDump(serviceId, fileFd, args);
} catch (error) {
  console.error(`error code: ${(error as BusinessError).code}, error msg: ${(error as BusinessError).message}`);
}

if (fileFd >= 0) {
  fileIo.closeSync(fileFd);
}

hidebug.startJsCpuProfiling⁹⁺

startJsCpuProfiling(filename: string) : void

Starts the VM profiling method. startJsCpuProfiling(filename: string) and stopJsCpuProfiling() are called in pairs. startJsCpuProfiling(filename: string) always occurs before stopJsCpuProfiling(). You are advised not to call either of these methods repeatedly. Otherwise, an exception may occur.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Parameters

Name	Type	Mandatory	Description
filename	string	Yes	User-defined file name of the sampling data. The .json file is generated in the files directory of the application based on the specified file name.

Error codes

For details about the error codes, see Universal Error Codes.

ID	Error Message
401	the parameter check failed,Parameter type error.

Example

import { hidebug } from '@kit.PerformanceAnalysisKit';
import { BusinessError } from '@kit.BasicServicesKit';

try {
  hidebug.startJsCpuProfiling("cpu_profiling");
  // ...
  hidebug.stopJsCpuProfiling();
} catch (error) {
  console.error(`error code: ${(error as BusinessError).code}, error msg: ${(error as BusinessError).message}`);
}

hidebug.stopJsCpuProfiling⁹⁺

stopJsCpuProfiling() : void

Stops the VM profiling method. stopJsCpuProfiling() and startJsCpuProfiling(filename: string) are called in pairs. startJsCpuProfiling() always occurs before stopJsCpuProfiling(). You are advised not to call either of these methods repeatedly. Otherwise, an exception may occur.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Example

import { hidebug } from '@kit.PerformanceAnalysisKit';
import { BusinessError } from '@kit.BasicServicesKit';

try {
  hidebug.startJsCpuProfiling("cpu_profiling");
  // ...
  hidebug.stopJsCpuProfiling();
} catch (error) {
  console.error(`error code: ${(error as BusinessError).code}, error msg: ${(error as BusinessError).message}`);
}

hidebug.dumpJsHeapData⁹⁺

dumpJsHeapData(filename: string) : void

Exports the heap data.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Parameters

Name	Type	Mandatory	Description
filename	string	Yes	User-defined file name of the sampling data. The .heapsnapshot file is generated in the files directory of the application based on the specified file name.

Error codes

For details about the error codes, see Universal Error Codes.

ID	Error Message
401	the parameter check failed, Parameter type error.

Example

import { hidebug } from '@kit.PerformanceAnalysisKit';
import { BusinessError } from '@kit.BasicServicesKit';

try {
  hidebug.dumpJsHeapData("heapData");
} catch (error) {
  console.error(`error code: ${(error as BusinessError).code}, error msg: ${(error as BusinessError).message}`);
}

hidebug.startProfiling^(deprecated)

startProfiling(filename: string) : void

NOTE

This API is deprecated since API version 9. You are advised to use hidebug.startJsCpuProfiling.

Starts the VM profiling method. startProfiling(filename: string) and stopProfiling() are called in pairs. startProfiling(filename: string) always occurs before stopProfiling(). You are advised not to call either of these methods repeatedly. Otherwise, an exception may occur.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Parameters

Name	Type	Mandatory	Description
filename	string	Yes	User-defined file name of the sampling data. The .json file is generated in the files directory of the application based on the specified file name.

Example

import { hidebug } from '@kit.PerformanceAnalysisKit';

hidebug.startProfiling("cpuprofiler-20220216");
// code block
// ...
// code block
hidebug.stopProfiling();

hidebug.stopProfiling^(deprecated)

stopProfiling() : void

NOTE

This API is deprecated since API version 9. You are advised to use hidebug.stopJsCpuProfiling.

Stops the VM profiling method. stopProfiling() and startProfiling(filename: string) are called in pairs. startProfiling(filename: string) always occurs before stopProfiling(). You are advised not to call either of these methods repeatedly. Otherwise, an exception may occur.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Example

import { hidebug } from '@kit.PerformanceAnalysisKit';

hidebug.startProfiling("cpuprofiler-20220216");
// code block
// ...
// code block
hidebug.stopProfiling();

hidebug.dumpHeapData^(deprecated)

dumpHeapData(filename: string) : void

NOTE

This API is deprecated since API version 9. You are advised to use hidebug.dumpJsHeapData.

Exports the VM heap data and generates a filename.heapsnapshot file.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Parameters

Name	Type	Mandatory	Description
filename	string	Yes	User-defined heap file name. The .heapsnapshot file is generated in the files directory of the application based on the specified file name.

Example

import { hidebug } from '@kit.PerformanceAnalysisKit';

hidebug.dumpHeapData("heap-20220216");

hidebug.getAppVMMemoryInfo¹²⁺

getAppVMMemoryInfo(): VMMemoryInfo

Obtains VM memory information.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Return value

Type	Description
VMMemoryInfo	VM memory information.

Example

import { hidebug } from '@kit.PerformanceAnalysisKit';

let vmMemory: hidebug.VMMemoryInfo = hidebug.getAppVMMemoryInfo();
console.info(`totalHeap = ${vmMemory.totalHeap}, heapUsed = ${vmMemory.heapUsed},` +
  `allArraySize = ${vmMemory.allArraySize}` );

hidebug.getAppThreadCpuUsage¹²⁺

getAppThreadCpuUsage(): ThreadCpuUsage[]

Obtains the CPU usage of application threads.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Return value

Type	Description
ThreadCpuUsage[]	CPU usage of all threads of the current application process.

Example

import { hidebug } from '@kit.PerformanceAnalysisKit';

let appThreadCpuUsage: hidebug.ThreadCpuUsage[] = hidebug.getAppThreadCpuUsage();
for (let i = 0; i < appThreadCpuUsage.length; i++) {
  console.info(`threadId=${appThreadCpuUsage[i].threadId}, cpuUsage=${appThreadCpuUsage[i].cpuUsage}`);
}

hidebug.startAppTraceCapture¹²⁺

startAppTraceCapture(tags: number[], flag: TraceFlag, limitSize: number) : string

Starts automatic trace collection in a specified scope. This API is a supplement to the HiTrace module. The performance consumption during trace collection increases with the collection scope. Therefore, before using this API, you are advised to run the hitrace command to capture trace logs and select the key scope of trace collection to improve the API performance.

startAppTraceCapture() and stopAppTraceCapture() must be called in pairs. Repeat calling of startAppTraceCapture() will cause exceptions. Trace collection consumes a lot of performance resources. Therefore, call stopAppTraceCapture() immediately after trace collection is complete.

When an application calls startAppTraceCapture() to collect trace data and the size of the data exceeds the value of limitSize, the system automatically calls stopAppTraceCapture() to stop trace collection. Therefore, if limitSize is set improperly, the generated trace data is insufficient for fault analysis. Therefore, you need to evaluate the value of limitSize as required.

Evaluation method: limitSize = Expected trace collection duration x Unit trace traffic.

Expected trace collection duration: You can determine the duration based on the fault scenario. The unit is second.

Unit trace traffic: The size of trace data generated by an application per second. The recommended value is 300 KB/s. You are advised to use the actual value of your application. The unit is KB/s.

To obtain the unit trace traffic of an application, you can call startAppTraceCapture() with limitSize set to the maximum value 500 MB. After N seconds, call stopAppTraceCapture() to stop the collection and check the size S (KB) of the trace data. The unit trace traffic is S/N (KB/s).

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Parameters

Name	Type	Mandatory	Description
tags	number[]	Yes	Scope for trace collection. For details, see tags.
flag	TraceFlag	Yes	For details, see TraceFlag.
limitSize	number	Yes	Limit on the trace file size, in bytes. The maximum size of a single file is 500 MB.

Return value

Type	Description
string	Path of the trace file.

Error codes

For details about the error codes, see HiDebug Error Codes.

ID	Error Message
401	Invalid argument, Possible causes:1.The limit parameter is too small 2.The parameter is not within the enumeration type 3.The parameter type error or parameter order error.
11400102	Capture trace already enabled.
11400103	No write permission on the file.
11400104	Abnormal trace status.

Example

import { hidebug } from '@kit.PerformanceAnalysisKit';
import { BusinessError } from '@kit.BasicServicesKit';

let tags: number[] = [hidebug.tags.ABILITY_MANAGER, hidebug.tags.ARKUI];
let flag: hidebug.TraceFlag = hidebug.TraceFlag.MAIN_THREAD;
let limitSize: number = 1024 * 1024;

try {
  let fileName: string = hidebug.startAppTraceCapture(tags, flag, limitSize);
  // code block
  // ...
  // code block
  hidebug.stopAppTraceCapture();
} catch (error) {
  console.error(`error code: ${(error as BusinessError).code}, error msg: ${(error as BusinessError).message}`);
}

hidebug.stopAppTraceCapture¹²⁺

stopAppTraceCapture() : void

Stops application trace collection. Use startAppTraceCapture() to start collection before calling this API. If this API is called before trace collection or it is repeatedly called, an exception will occur.

If startAppTraceCapture () is called without a properly specified limitSize, the size of the generated trace may exceed the limitSize value, causing the system to automatically call stopAppTraceCapture(). In this case, if stopAppTraceCapture() is called again, an error code 11400105 will be displayed.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Error codes

For details about the error codes, see HiDebug Error Codes.

ID	Error Message
11400104	The status of the trace is abnormal.
11400105	No capture trace running.

Example

import { hidebug } from '@kit.PerformanceAnalysisKit';
import { BusinessError } from '@kit.BasicServicesKit';

let tags: number[] = [hidebug.tags.ABILITY_MANAGER, hidebug.tags.ARKUI];
let flag: hidebug.TraceFlag = hidebug.TraceFlag.MAIN_THREAD;
let limitSize: number = 1024 * 1024;
try {
  let fileName: string = hidebug.startAppTraceCapture(tags, flag, limitSize);
  // code block
  // ...
  // code block
  hidebug.stopAppTraceCapture();
} catch (error) {
  console.error(`error code: ${(error as BusinessError).code}, error msg: ${(error as BusinessError).message}`);
}

hidebug.getAppMemoryLimit¹²⁺

getAppMemoryLimit() : MemoryLimit

Obtains the memory limit of an application process.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Return value

Type	Description
MemoryLimit	Defines the memory limit of the application process.

Example

import { hidebug } from '@kit.PerformanceAnalysisKit';

let appMemoryLimit:hidebug.MemoryLimit = hidebug.getAppMemoryLimit();

hidebug.getSystemCpuUsage¹²⁺

getSystemCpuUsage() : number

Obtains the CPU usage of the system.

For example, if the CPU usage of system resources is 50%, 0.5 is returned.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Return value

Type	Description
number	CPU usage of the system.

Error codes

For details about the error codes, see HiDebug CPU Usage Error Codes.

ID	Error Message
11400104	The status of the system CPU usage is abnormal.

Example

import { hidebug } from '@kit.PerformanceAnalysisKit';
import { BusinessError } from '@kit.BasicServicesKit';

try {
  console.info(`getSystemCpuUsage: ${hidebug.getSystemCpuUsage()}`)
} catch (error) {
  console.error(`error code: ${(error as BusinessError).code}, error msg: ${(error as BusinessError).message}`);
}

hidebug.setAppResourceLimit¹²⁺

setAppResourceLimit(type: string, value: number, enableDebugLog: boolean) : void

Sets the number of FDs, number of threads, JS memory, or native memory limit of the application.

NOTE

This API is valid only when the Developer options is enabled.

Atomic service API: This API can be used in atomic services since API version 12.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Parameters

Name	Type	Mandatory	Description
type	string	Yes	Types of leak resources: - pss_memory (native memory) - js_heap (JavaScript heap memory) - fd (file descriptor) - thread (thread)
value	number	Yes	Value range of the maximum values of the leak resource types: - pss_memory: [1024, 4 x 1024 x 1024] (Unit: KB) - js_heap: [85, 95] (85% to 95% of the upper size limit of the JS heap memory) - fd: [10, 10000] - thread: [1, 1000]
enableDebugLog	boolean	Yes	Whether to enable external debug log. The default value is false. Set this parameter to true only in the gray version because collecting debug logs consumes too much CPU or memory.

Error codes

For details about the error codes, see HiDebug Error Codes.

ID	Error Message
401	Invalid argument, Possible causes:1.The limit parameter is too small 2.The parameter is not in the specified type 3.The parameter type error or parameter order error.
11400104	Set limit failed due to remote exception.

Example

import { hidebug } from '@kit.PerformanceAnalysisKit';
import { BusinessError } from '@kit.BasicServicesKit';

let type: string = 'js_heap';
let value: number = 85;
let enableDebugLog: boolean = false;
try {
  hidebug.setAppResourceLimit(type, value, enableDebugLog);
} catch (error) {
  console.error(`error code: ${(error as BusinessError).code}, error msg: ${(error as BusinessError).message}`);
}

hidebug.getAppNativeMemInfo¹²⁺

getAppNativeMemInfo(): NativeMemInfo

Obtains the memory information of the application process. This API is implemented by reading data from the /proc/{pid}/smaps_rollup and /proc/{pid}/statm node.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

NOTE

Reading the /proc/{pid}/smaps_rollup node is time-consuming. Therefore, you are advised not to use this API in the main thread. You can use this API in the asynchronous thread started by calling @ohos.taskpool or @ohos.worker to avoid frame freezing.

Return value

Type	Description
NativeMemInfo	Memory information of the application process.

Example

import { hidebug } from '@kit.PerformanceAnalysisKit';

let nativeMemInfo: hidebug.NativeMemInfo = hidebug.getAppNativeMemInfo();
console.info(`pss: ${nativeMemInfo.pss}, vss: ${nativeMemInfo.vss}, rss: ${nativeMemInfo.rss}, ` +
  `sharedDirty: ${nativeMemInfo.sharedDirty}, privateDirty: ${nativeMemInfo.privateDirty}, ` +
  `sharedClean: ${nativeMemInfo.sharedClean}, privateClean: ${nativeMemInfo.privateClean}`);

hidebug.getSystemMemInfo¹²⁺

getSystemMemInfo(): SystemMemInfo

Obtains system memory information. This API is implemented by reading data from the /proc/meminfo node.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Return value

Type	Description
SystemMemInfo	System memory information.

Example

import { hidebug } from '@kit.PerformanceAnalysisKit';

let systemMemInfo: hidebug.SystemMemInfo = hidebug.getSystemMemInfo();

console.info(`totalMem: ${systemMemInfo.totalMem}, freeMem: ${systemMemInfo.freeMem}, ` +
  `availableMem: ${systemMemInfo.availableMem}`);

hidebug.getVMRuntimeStats¹²⁺

getVMRuntimeStats(): GcStats

Obtains all system GC statistics.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Return value

Type	Description
GcStats	System GC statistics.

Example

import { hidebug } from '@kit.PerformanceAnalysisKit';

let vMRuntimeStats: hidebug.GcStats = hidebug.getVMRuntimeStats();
console.info(`gc-count: ${vMRuntimeStats['ark.gc.gc-count']}`);
console.info(`gc-time: ${vMRuntimeStats['ark.gc.gc-time']}`);
console.info(`gc-bytes-allocated: ${vMRuntimeStats['ark.gc.gc-bytes-allocated']}`);
console.info(`gc-bytes-freed: ${vMRuntimeStats['ark.gc.gc-bytes-freed']}`);
console.info(`fullgc-longtime-count: ${vMRuntimeStats['ark.gc.fullgc-longtime-count']}`);

hidebug.getVMRuntimeStat¹²⁺

getVMRuntimeStat(item: string): number

Obtains the specified system GC statistics based on parameters.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Parameters

Name	Type	Mandatory	Description
item	string	Yes	Item of the GC statistics to be obtained.

Input Parameter	Return Value Description
ark.gc.gc-count	Count of GC of the calling thread.
ark.gc.gc-time	GC time triggered by the calling thread, in milliseconds.
ark.gc.gc-bytes-allocated	Memory size allocated to the Ark VM of the calling thread, in bytes.
ark.gc.gc-bytes-freed	Memory freed by the GC of the calling thread, in bytes.
ark.gc.fullgc-longtime-count	Count of long fullGC of the calling thread.

Error codes

ID	Error Message
401	Possible causes:1. Invalid parameter, a string parameter required. 2. Invalid parameter, unknown property.

Example

import { hidebug } from '@kit.PerformanceAnalysisKit';
import { BusinessError } from '@kit.BasicServicesKit';

try {
  console.info(`gc-count: ${hidebug.getVMRuntimeStat('ark.gc.gc-count')}`);
  console.info(`gc-time: ${hidebug.getVMRuntimeStat('ark.gc.gc-time')}`);
  console.info(`gc-bytes-allocated: ${hidebug.getVMRuntimeStat('ark.gc.gc-bytes-allocated')}`);
  console.info(`gc-bytes-freed: ${hidebug.getVMRuntimeStat('ark.gc.gc-bytes-freed')}`);
  console.info(`fullgc-longtime-count: ${hidebug.getVMRuntimeStat('ark.gc.fullgc-longtime-count')}`);
} catch (error) {
  console.error(`error code: ${(error as BusinessError).code}, error msg: ${(error as BusinessError).message}`);
}

MemoryLimit¹²⁺

Defines the memory limit of the application process.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Name	Type	Mandatory	Description
rssLimit	bigint	Yes	Limit on the resident set size, in KB.
vssLimit	bigint	Yes	Limit on the virtual memory size, in KB.
vmHeapLimit	bigint	Yes	Limit on the JS VM heap size of the calling thread, in KB.
vmTotalHeapSize	bigint	Yes	Size limit of the JS heap memory of the process, in KB.

VMMemoryInfo¹²⁺

Describes the VM memory information.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Name	Type	Readable	Writable	Description
totalHeap	bigint	Yes	No	Total heap size of the current VM, in KB.
heapUsed	bigint	Yes	No	Heap size used by the current VM, in KB.
allArraySize	bigint	Yes	No	Size of all array objects of the current VM, in KB.

ThreadCpuUsage¹²⁺

Describes the CPU usage of a thread.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Name	Type	Readable	Writable	Description
threadId	number	Yes	No	Thread ID.
cpuUsage	number	Yes	No	CPU usage of the thread.

hidebug.tags¹²⁺

Enumerates the tags used in trace collection. You can use the HiTrace commands to capture the trace data of a specified tag.

NOTE

The following tag values are defined by the system and may change with the version upgrade. To avoid compatibility issues after the upgrade, use the tag names instead of the tag values in application development.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Name	Type	Read Only	Description
ABILITY_MANAGER	number	Yes	Capability management. The corresponding HiTrace command is tagName:ability.
ARKUI	number	Yes	ArkUI development framework. The corresponding HiTrace command is tagName:ace.
ARK	number	Yes	JSVM VM. The corresponding HiTrace command is tagName:ark.
BLUETOOTH	number	Yes	Bluetooth. The corresponding HiTrace command is tagName:bluetooth.
COMMON_LIBRARY	number	Yes	Common library subsystem. The corresponding HiTrace command is tagName:commonlibrary.
DISTRIBUTED_HARDWARE_DEVICE_MANAGER	number	Yes	Distributed hardware device management. The corresponding HiTrace command is tagName:devicemanager.
DISTRIBUTED_AUDIO	number	Yes	Distributed audio. The corresponding HiTrace command is tagName:daudio.
DISTRIBUTED_CAMERA	number	Yes	Distributed camera. The corresponding HiTrace command is tagName:dcamera.
DISTRIBUTED_DATA	number	Yes	Distributed data management. The corresponding HiTrace command is tagName:distributeddatamgr.
DISTRIBUTED_HARDWARE_FRAMEWORK	number	Yes	Distributed hardware framework. The corresponding HiTrace command is tagName:dhfwk.
DISTRIBUTED_INPUT	number	Yes	Distributed input. The corresponding HiTrace command is tagName:dinput.
DISTRIBUTED_SCREEN	number	Yes	Distributed screen. The corresponding HiTrace command is tagName:dscreen.
DISTRIBUTED_SCHEDULER	number	Yes	Distributed scheduler. The corresponding HiTrace command is tagName:dsched.
FFRT	number	Yes	FFRT task. The corresponding HiTrace command is tagName:ffrt.
FILE_MANAGEMENT	number	Yes	File management system. The corresponding HiTrace command is tagName:filemanagement.
GLOBAL_RESOURCE_MANAGER	number	Yes	Global resource management. The corresponding HiTrace command is tagName:gresource.
GRAPHICS	number	Yes	Graphics module. The corresponding HiTrace command is tagName:graphic.
HDF	number	Yes	HDF subsystem. The corresponding HiTrace command is tagName:hdf.
MISC	number	Yes	MISC module. The corresponding HiTrace command is tagName:misc.
MULTIMODAL_INPUT	number	Yes	Multi-modal input module. The corresponding HiTrace command is tagName:multimodalinput.
NET	number	Yes	Network. The corresponding HiTrace command is tagName:net.
NOTIFICATION	number	Yes	Notification module. The corresponding HiTrace command is tagName:notification.
NWEB	number	Yes	Nweb. The corresponding HiTrace command is tagName:nweb.
OHOS	number	Yes	OHOS. The corresponding HiTrace command is tagName:ohos.
POWER_MANAGER	number	Yes	Power management. The corresponding HiTrace command is tagName:power.
RPC	number	Yes	RPC. The corresponding HiTrace command is tagName:rpc.
SAMGR	number	Yes	System capability management. The corresponding HiTrace command is tagName:samgr.
WINDOW_MANAGER	number	Yes	Window management. The corresponding HiTrace command is tagName:window.
AUDIO	number	Yes	Audio module. The corresponding HiTrace command is tagName:zaudio.
CAMERA	number	Yes	Camera module. The corresponding HiTrace command is tagName:zcamera.
IMAGE	number	Yes	Image module. The corresponding HiTrace command is tagName:zimage.
MEDIA	number	Yes	Media module. The corresponding HiTrace command is tagName:zmedia.

NativeMemInfo¹²⁺

Describes memory information of the application process.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Name	Type	Mandatory	Description
pss	bigint	Yes	Size of the occupied physical memory (including the proportionally allocated memory occupied by the shared library), in KB. The value of this parameter is obtained by summing up the values of Pss and SwapPss in the /proc/{pid}/smaps_rollup node.
vss	bigint	Yes	Size of the occupied virtual memory (including the memory occupied by the shared library), in KB. The value of this parameter is obtained by multiplying the value of size in the /proc/{pid}/statm node by 4.
rss	bigint	Yes	Size of the occupied physical memory (including the memory occupied by the shared library), in KB. The value of this parameter is obtained by reading the value of Rss in the /proc/{pid}/smaps_rollup node.
sharedDirty	bigint	Yes	Size of the shared dirty memory, in KB. The value of this parameter is obtained by reading the value of Shared_Dirty in the /proc/{pid}/smaps_rollup node.
privateDirty	bigint	Yes	Size of the private dirty memory, in KB. The value of this parameter is obtained by reading the value of Private_Dirty in the /proc/{pid}/smaps_rollup node.
sharedClean	bigint	Yes	Size of the shared clean memory, in KB. The value of this parameter is obtained by reading the value of Shared_Clean in the /proc/{pid}/smaps_rollup node.
privateClean	bigint	Yes	Size of the private clean memory, in KB. The value of this parameter is obtained by reading the value of Private_Clean in the /proc/{pid}/smaps_rollup node.

SystemMemInfo¹²⁺

Describes the system memory information, including the total memory, free memory, and available memory.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Name	Type	Mandatory	Description
totalMem	bigint	Yes	Total memory of the system, in KB. The value of this parameter is obtained by reading the value of MemTotal in the /proc/meminfo node.
freeMem	bigint	Yes	Free memory of the system, in KB. The value of this parameter is obtained by reading the value of MemFree in the /proc/meminfo node.
availableMem	bigint	Yes	Available memory of the system, in KB. The value of this parameter is obtained by reading the value of MemAvailable in the /proc/meminfo node.

TraceFlag¹²⁺

Describes types of trace collection threads, including the main thread and all threads.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Name	Value	Description
MAIN_THREAD	1	The main thread of the application.
ALL_THREADS	2	All threads of the application.

GcStats¹²⁺

type GcStats = Record&lt;string, number&gt;

Describes the key-value pair used to store GC statistics. This type does not support multi-thread operations. If this type is operated by multiple threads at the same time in an application, use a lock for it.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Type	Description
Record<string, number>	Key-value pair format used to store GC statistics.

GcStats contains the following information:

Name	Type	Description
ark.gc.gc-count	number	Count of GC of the calling thread.
ark.gc.gc-time	number	GC time triggered by the calling thread, in milliseconds.
ark.gc.gc-bytes-allocated	number	Memory size allocated to the Ark VM of the calling thread, in bytes.
ark.gc.gc-bytes-freed	number	Memory freed by the GC of the calling thread, in bytes.
ark.gc.fullgc-longtime-count	number	Count of long fullGC of the calling thread.

hidebug.isDebugState¹²⁺

isDebugState(): boolean

Obtains the debugging state of an application process. If the Ark or native layer of the application process is in debugging state, true is returned. Otherwise, false is returned.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Return value

Type	Description
boolean	Whether an application process is in the debugging state.

Example

import { hidebug } from '@kit.PerformanceAnalysisKit';

console.info(`isDebugState = ${hidebug.isDebugState()}`)

hidebug.getGraphicsMemory¹⁴⁺

getGraphicsMemory(): Promise&lt;number&gt;

Obtains the size of the GPU memory. This API uses a promise to return the result.

Atomic service API: This API can be used in atomic services since API version 14.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Return value

Type	Description
Promise<number>	Size of the GPU memory, in KB.

Error codes

ID	Error Message
11400104	Failed to get the application memory due to a remote exception.

Example

import { hidebug, hilog } from '@kit.PerformanceAnalysisKit';
import { BusinessError } from '@kit.BasicServicesKit';

hidebug.getGraphicsMemory().then((ret: number) => {
  console.info(`graphicsMemory: ${ret}`)
}).catch((error: BusinessError) => {
  console.error(`error code: ${error.code}, error msg: ${error.message}`);
})

hidebug.getGraphicsMemorySync¹⁴⁺

getGraphicsMemorySync(): number

Obtains the size of the GPU memory synchronously.

NOTE

This API involves multiple cross-process communications and may have performance problems. The asynchronous API getGraphicsMemory is recommended.

Atomic service API: This API can be used in atomic services since API version 14.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Return value

Type	Description
number	Size of the GPU memory, in KB.

Error codes

ID	Error Message
11400104	Failed to get the application memory due to a remote exception.

Example

import { hidebug } from '@kit.PerformanceAnalysisKit';
import { BusinessError } from '@kit.BasicServicesKit';

try {
  console.info(`graphicsMemory: ${hidebug.getGraphicsMemorySync()}`)
} catch (error) {
  console.error(`error code: ${(error as BusinessError).code}, error msg: ${(error as BusinessError).message}`);
}

hidebug.dumpJsRawHeapData¹⁸⁺

dumpJsRawHeapData(needGC?: boolean): Promise&lt;string&gt;

Dumps the original heap snapshot of the VM for the current thread. The API uses a promise to return the path of the .rawheap file. You can use rawheap-translator to convert the generated file into a .heapsnapshot file for parsing.

NOTE

This API is resource-consuming. Therefore, the calling frequency and times are strictly limited. You need to delete the files immediately after processing them. You are advised to use this API only in the gray testing version of an application.

Atomic service API: This API can be used in atomic services since API version 18.

System capability: SystemCapability.HiviewDFX.HiProfiler.HiDebug

Name	Type	Mandatory	Description
needGC	boolean	No	Whether GC is required when a heap snapshot is dumped. The default value is true. If this parameter is not specified, GC is triggered before dumping.

Return value

Type	Description
Promise<string>	Path of the generated snapshot file. (Application Sandbox)

Error codes

For details about the error codes, see HiDebug Error Codes.

ID	Error Message
11400106	Quota exceeded.
11400107	Fork operation failed.
11400108	Failed to wait for the child process to finish.
11400109	Timeout while waiting for the child process to finish.
11400110	Disk remaining space too low.
11400111	Napi interface call exception.
11400112	Repeated data dump.
11400113	Failed to create dump file.

Example

import { hidebug } from '@kit.PerformanceAnalysisKit';
import { BusinessError } from '@kit.BasicServicesKit';
hidebug.dumpJsRawHeapData().then((filePath: string) => {
  console.info(`dumpJsRawHeapData success and generated file path is ${filePath}`)
}).catch((error: BusinessError) => {
  console.error(`error code: ${error.code}, error msg: ${error.message}`);
})

你可能感兴趣的鸿蒙文章

harmony 鸿蒙Performance Analysis Kit

harmony 鸿蒙Performance Analysis Kit

harmony 鸿蒙HiAppEvent

harmony 鸿蒙HiAppEvent_AppEventGroup

harmony 鸿蒙HiAppEvent_AppEventInfo

harmony 鸿蒙HiCollie

harmony 鸿蒙HiCollie_DetectionParam

harmony 鸿蒙HiCollie_SetTimerParam

harmony 鸿蒙HiDebug

harmony 鸿蒙HiDebug_MemoryLimit