Lines Matching refs:memory
4 …memory debugging is to locate problems related to dynamic memory. The kernel provides a variety of…
12 …rmation includes the memory pool size, memory usage, remaining memory size, maximum free memory, m…
14 …dicates the maximum memory used in a memory pool. The waterline value is updated upon each memory …
16 …memory pool. If the fragmentation rate is high, there are a large number of free memory blocks in …
18 - You can use [APIs for memory management](kernel-mini-basic-memory.md) to scan node information in…
23 …memory information statistics function. This function is enabled by default. To disable the functi…
36 UINT32 totalUsedSize; // Memory usage of the memory pool.
37 UINT32 totalFreeSize; // Remaining size of the memory pool.
38 UINT32 maxFreeNodeSize; // Maximum size of the free memory block in the memory pool.
39 UINT32 usedNodeNum; // Number of non-free memory blocks in the memory pool.
40 UINT32 freeNodeNum; // Number of free memory blocks in the memory pool.
42 UINT32 usageWaterLine; // Waterline of the memory pool.
47 To obtain the memory waterline, call **LOS_MemInfoGet**. The first parameter in the API is the star…
49 …memory fragmentation rate, call **LOS_MemInfoGet** to obtain the remaining memory size and the max…
56 1. Create a monitoring task to obtain information about the memory pool.
58 2. Calls **LOS_MemInfoGet** to obtain the basic information about the memory pool.
60 3. Calculate the memory usage and fragmentation rate.
81 …/* pool is the memory address of the information to be collected. OS_SYS_MEM_ADDR is used as an ex…
84 /* Calculate the fragmentation rate of the memory pool. */
86 /* Calculate the memory usage of the memory pool. */
126 …memory leak check is used to locate dynamic memory leak problems. After this function is enabled, …
131 **LOSCFG_MEM_LEAKCHECK** specifies the setting of the memory leak check. This function is disabled …
133 …number of LRs recorded. The default value is **3**. Each LR consumes the memory of **sizeof(void \…
141 Correctly setting this macro can ignore invalid LRs and reduce memory consumption.
149 …memory leak in key code logic. If this function is enabled, LR information is recorded each time w…
151 …ze. Columns 3 to 5 list the LR addresses. You can determine the specific memory location of the no…
166 > Enabling memory leak check affects memory application performance. LR addresses will be recorded …
175 2. Simulate a memory leak by requesting memory without releasing it.
179 4. Compare the logs to obtain information about the node where a memory leak occurred.
192 After the memory check function is enabled, other tasks running on certain platforms may frequently…
236 …etween the two logs is as follows. The following memory nodes are suspected to have blocks with a …
269 The memory node addressed by **0x080041ee** is not released after being requested in **MemLeakTest*…
276 …el, memory corruption check is used to check the integrity of a dynamic memory pool. This mechanis…
281 **LOSCFG_BASE_MEM_NODE_INTEGRITY_CHECK** specifies the setting of the memory corruption check. This…
283 1. If this macro is enabled, the memory pool integrity will be checked in real time upon each memor…
285 2. If this macro is not enabled, you can call **LOS_MemIntegrityCheck** to check the memory pool in…
287 …memory node and provides information about the previous node (because memory is contiguous, a node…
291 …memory corruption check is enabled, a magic number is added to the node header, which increases th…
299 …eck for memory corruption by calling **LOS_MemIntegrityCheck**. If no memory corruption occurs, **…
306 1. Request two physically adjacent memory blocks.
310 3. Call **LOS_MemIntegrityCheck** to check whether memory corruption occurs.
332 /* Request two physically adjacent memory blocks. */
335 …ess to cause memory corruption. The memory block of the first node is 8 bytes. Clearing 12 bytes o…
350 [ERR][IT_TST_INI][OsMemMagicCheckPrint], 1664, memory check error!
351 memory used but magic num wrong, magic num = 0x0
356 /*The node LR information can be output only after the memory leak check is enabled. */