/ohos5.0/docs/en/application-dev/napi/ |
H A D | use-napi-about-cleanuphook.md | 9 Before using Node-API to add or remove cleanup hooks, understand the following concepts: 14 … in ArkTS and cleanup hook functions. Read on to learn the Node-API interfaces that you can use to… 18 The following table lists the APIs for using different types of cleanup hooks. 22 | napi_remove_env_cleanup_hook | Removes an environment cleanup hook function.| 24 | napi_remove_async_cleanup_hook | Removes an async cleanup hook function.| 60 // Perform the cleanup operation. 63 // Create an external buffer and add the environment cleanup hook function. 72 // Create an external buffer object and specify the cleanup callback function. 90 // Remove the environment cleanup hook function immediately. 186 // Create and trigger an async cleanup operation in an event loop. [all …]
|
H A D | napi-data-types-interfaces.md | 148 Value used to add a callback for an async operation. It is mainly used to perform a cleanup operati… 715 | napi_add_env_cleanup_hook | Adds a cleanup hook function for releasing resources when the environ… 716 | napi_remove_env_cleanup_hook | Removes a cleanup hook function.| 717 | napi_add_async_cleanup_hook | Adds an async cleanup hook function for releasing resources when th… 718 | napi_remove_async_cleanup_hook | Removes an async cleanup hook function.|
|
H A D | use-napi-about-buffer.md | 288 // Perform the cleanup operation, for example, release memory.
|
H A D | use-napi-life-cycle.md | 20 - GC callback: You can register GC callbacks to perform specific cleanup operations when ArkTS obje…
|
H A D | use-napi-faqs.md | 165 OH_LOG_WARN(LOG_APP, "cleanup is called");
|
/ohos5.0/foundation/communication/bluetooth_service/services/bluetooth/stack/platform/include/ |
H A D | module.h | 31 void (*cleanup)(); member
|
/ohos5.0/foundation/multimedia/audio_framework/frameworks/native/audioutils/include/ |
H A D | audio_utils_c.h | 25 #define AUTO_CLEANUP(func) __attribute__((cleanup(func)))
|
/ohos5.0/foundation/communication/bluetooth_service/services/bluetooth/stack/platform/src/ |
H A D | module.c | 72 module->cleanup(); in ModuleCleanup()
|
/ohos5.0/foundation/communication/bluetooth_service/services/bluetooth/stack/src/avdtp/ |
H A D | avdtp.c | 94 .cleanup = AVDT_Cleanup,
|
/ohos5.0/foundation/arkui/ace_engine/test/tools/event_tree_to_graph/src/graph/ |
H A D | graph_converter.py | 149 dot.render(out_graph_file_name, format='svg', cleanup=True, view=False) 228 dot.render(out_graph_file_name, format='svg', cleanup=True, view=False)
|
/ohos5.0/foundation/communication/bluetooth_service/services/bluetooth/stack/src/avctp/ |
H A D | avctp.c | 121 .cleanup = AVCT_Cleanup,
|
/ohos5.0/foundation/communication/dsoftbus/adapter/common/include/ |
H A D | softbus_adapter_thread.h | 123 __attribute__((cleanup(SoftBusMutexUnlockAuto), unused)) SoftBusMutex *lockGuard##mutex = &mutex
|
/ohos5.0/foundation/graphic/graphic_3d/lume/LumeBinaryCompile/LumeShaderCompiler/src/ |
H A D | json.h | 148 cleanup(); 179 cleanup(); in ~value() 182 void cleanup() in cleanup() function
|
/ohos5.0/foundation/graphic/graphic_3d/lume/LumeEngine/api/core/json/ |
H A D | json.h | 203 cleanup(); in CORE_BEGIN_NAMESPACE() 274 cleanup(); in CORE_BEGIN_NAMESPACE() 360 cleanup(); in CORE_BEGIN_NAMESPACE() 371 void cleanup() in CORE_BEGIN_NAMESPACE() function
|
/ohos5.0/docs/zh-cn/application-dev/napi/ |
H A D | use-napi-faqs.md | 162 OH_LOG_WARN(LOG_APP, "cleanup is called"); 171 // cleanup 提前释放线程安全函数, 为避免UAF, 将释放工作交给调用方
|
/ohos5.0/docs/en/application-dev/reference/apis-backgroundtasks-kit/ |
H A D | js-apis-backgroundTaskManager-sys.md | 7 …on and exits the application, the application can request a transient task to complete the cleanup.
|
/ohos5.0/foundation/communication/bluetooth_service/services/bluetooth/stack/src/att/ |
H A D | att_init.c | 330 .cleanup = ATT_Clearup,
|
/ohos5.0/base/update/packaging_tools/ |
H A D | utils.py | 516 target_package_temp_obj.cleanup() 519 source_package_temp_obj.cleanup()
|
/ohos5.0/base/hiviewdfx/faultloggerd/interfaces/innerkits/unwinder/ |
H A D | arm_exidx_instructions.txt | 4 10000000 00000000 Refuse to unwind (for example, out of a cleanup) (see remark a)
|
/ohos5.0/docs/zh-cn/device-dev/device-test/ |
H A D | xts.md | 255 // Test suite cleanup action, which is executed after the last test case
|
H A D | xdevice.md | 659 "cleanup-apps": true
|
/ohos5.0/foundation/communication/bluetooth_service/services/bluetooth/stack/src/l2cap/ |
H A D | l2cap_if.c | 775 .cleanup = L2CIF_Finalize,
|
/ohos5.0/foundation/communication/bluetooth_service/services/bluetooth/stack/src/rfcomm/ |
H A D | rfcomm_api.c | 981 .cleanup = RFCOMM_Cleanup,
|
/ohos5.0/docs/en/application-dev/reference/common/ |
H A D | jsvm__types_8h.md | 56 …en the associated JavaScript object is reclaimed by the GC to execute the native cleanup action. |
|
/ohos5.0/docs/zh-cn/application-dev/reference/native-lib/ |
H A D | napi.md | 532 - OpenHarmony中,创建线程安全函数的过程中没有注册cleanup hook方法,如有需要可以调用napi_add_env_cleanup_hook。
|