| /ohos5.0/docs/en/release-notes/changelogs/v3.2-beta5/ |
| H A D | changelogs-security.md | 7 Behavior of released JavaScript APIs will be changed.
25 Behavior of released JavaScript APIs will be changed.
41 Behavior of released JavaScript APIs will be changed.
57 Behavior of released JavaScript APIs will be changed.
73 Behavior of released JavaScript APIs will be changed.
89 Behavior of released JavaScript APIs will be changed.
105 Behavior of released JavaScript APIs will be changed.
121 Behavior of released JavaScript APIs will be changed.
137 Behavior of released JavaScript APIs will be changed.
153 Behavior of released JavaScript APIs will be changed.
[all …]
|
| /ohos5.0/docs/en/release-notes/changelogs/OpenHarmony_3.2.10.1/ |
| H A D | changelog-security.md | 7 Behavior of released JavaScript APIs will be changed.
25 Behavior of released JavaScript APIs will be changed.
41 Behavior of released JavaScript APIs will be changed.
57 Behavior of released JavaScript APIs will be changed.
73 Behavior of released JavaScript APIs will be changed.
89 Behavior of released JavaScript APIs will be changed.
105 Behavior of released JavaScript APIs will be changed.
121 Behavior of released JavaScript APIs will be changed.
137 Behavior of released JavaScript APIs will be changed.
153 Behavior of released JavaScript APIs will be changed.
[all …]
|
| /ohos5.0/docs/en/application-dev/reference/apis-network-kit/ |
| H A D | _net_conn___net_conn_callback.md | 40 …e parameter memory is automatically cleared and therefore the parameter pointer should be released.
60 …e parameter memory is automatically cleared and therefore the parameter pointer should be released.
81 …e parameter memory is automatically cleared and therefore the parameter pointer should be released.
102 …e parameter memory is automatically cleared and therefore the parameter pointer should be released.
|
| /ohos5.0/docs/en/contribute/ |
| H A D | OpenHarmony-security-test-guide.md | 17 - Perform consistency check of the released versions, and check that the [released version images](…
43 … The version security test report is released with the entire test report of the version, instead …
|
| /ohos5.0/docs/en/design/ |
| H A D | OpenHarmony-API-governance.md | 7 …w.openharmony.cn/pmc) for release. Any revision to this Charter will be released only after being …
99 …1. Canary version: API Preview version released at an earlier date, which cannot ensure API stabil…
102 1. Beta version: publicly released beta version, which cannot ensure API stability.
106 …1. The APIs are frozen after the API Stable version is released. API additions or changes are not …
108 …es cannot be made on released APIs, and deprecation of released APIs is restricted. The basic requ…
111 1. Retain the deprecated APIs in at least five API versions released since the deprecation.
|
| /ohos5.0/docs/en/release-notes/changelogs/OpenHarmony_4.1.5.5/ |
| H A D | changelogs-file_manager.md | 15 This API has never been released with a formal version. No adaptation is required.
37 This API has never been released with a formal version. No adaptation is required.
|
| /ohos5.0/docs/en/application-dev/internationalization/ |
| H A D | linguistic-testing.md | 3 … content comply with local usage habits before the application is officially released and launched.
5 …y minor error may cause user churn. Therefore, before an application is released globally, linguis…
|
| /ohos5.0/docs/en/application-dev/file-management/ |
| H A D | native-fileuri-guidelines.md | 45 …iFromPath** to obtain the URI from a path. The memory allocated must be released using **free()**.…
64 …hFromUri** to convert the URI into a path. The memory allocated must be released using **free()**.…
83 …ectory where the specified URI is located. The memory allocated must be released using **free()**.…
115 …me** to obtain the file name from the URI. The memory allocated must be released using **free()**.…
|
| H A D | native-environment-guidelines.md | 39 …x path of the user **Download** directory. The memory allocated must be released using **free()**.…
54 …ox path of the user **Desktop** directory. The memory allocated must be released using **free()**.…
69 … path of the user **Documents** directory. The memory allocated must be released using **free()**.…
|
| /ohos5.0/docs/en/device-dev/kernel/ |
| H A D | kernel-small-basic-trans-mutex.md | 20 …n set to the upper limit value of the mutex priority. When the mutex is released, the task priorit…
30 … mutex held by another task or attempt to release a mutex that has been released will return an er…
34 …to release the mutex held by another task, or attempts to release the mutex that has been released.
41 …sk, the mutex is locked. Other tasks will be blocked until the mutex is released by the task. The …
75 …ue will be executed. The blocked task can be unlocked and executed only when the mutex is released.
77 …ll be executed. The blocked task can be executed only when the mutex is released within the specif…
81 …ex, the task with a higher priority will be unblocked when the mutex is released. The unblocked ta…
83 - If no task is blocked by the specified mutex, the mutex is released successfully.
92 …cheduling and avoid long-time task blocking. Therefore, a mutex must be released as soon as possib…
|
| H A D | kernel-small-basic-trans-rwlock.md | 63 …is held by another task, the task cannot acquire the lock until the lock in write mode is released.
69 … task has a higher priority, the current task is suspended until the lock in read mode is released.
76 - If no task is blocked by the specified RW lock, the RW lock is released.
83 …heduling and avoid long-time task blocking. Therefore, RW locks must be released as soon as possib…
|
| H A D | kernel-mini-basic-ipc-mutex.md | 17 …sk, the mutex is locked. Other tasks will be blocked until the mutex is released by the task. The …
44 …ll be executed. The blocked task can be executed only when the mutex is released within the specif…
47 …ex, the task with a higher priority will be unblocked when the mutex is released. The unblocked ta…
48 - If no task is blocked by the specified mutex, the mutex is released successfully.
53 …he same task, the application is considered successful, and the lock is released based on the numb…
57 …cheduling and avoid long-time task blocking. Therefore, a mutex must be released as soon as possib…
|
| H A D | kernel-small-debug-user.md | 7 …tion. The memory node integrity is checked when memory is requested and released by an application…
18 When memory is released, the system matches the memory node control block based on the memory addre…
32 When memory is released, the input parameter pointer in the **free** API is used to match the **ptr…
43 …a linked list with the thread ID as the header. When the heap memory is released, the correspondin…
52 …ged by a wild pointer cannot be identified. When memory is allocated or released, the memory node …
58 …When heap memory is released by **free**, the memory block is not released immediately. Instead, t…
519 …Read operation: If the magic number (0xFEFEFEFE) is read from the memory block released, UAF occur…
523 …released to the heap memory pool immediately. Instead, the heap memory is placed in a queue with a…
530 …**mmap** API via **malloc**. If the heap memory is accessed after being released, the user program…
|
| /ohos5.0/docs/en/application-dev/dfx/ |
| H A D | hiappevent-watcher-address-sanitizer-events.md | 31 | double-free | The same memory address is released more than once.|
35 | heap-use-after-free | The released heap memory is used.|
38 | new-delete-type-mismatch | The released memory size does not match the allocated memory size.|
|
| /ohos5.0/docs/zh-cn/application-dev/reference/apis-ability-kit/ |
| H A D | js-apis-app-ability-uiAbility.md | 573 | 16200001 | Caller released. The caller has been released. |
661 | 16200001 | Caller released. The caller has been released. |
737 | 16200001 | Caller released. The caller has been released. |
790 | 16200001 | Caller released. The caller has been released. |
844 | 16200001 | Caller released. The caller has been released. |
900 | 16200001 | Caller released. The caller has been released. |
|
| H A D | js-apis-inner-application-uiAbilityContext-sys.md | 77 | 16200001 | The caller has been released. |
172 | 16200001 | The caller has been released. |
275 | 16200001 | The caller has been released. |
349 | 16200001 | The caller has been released. |
419 | 16200001 | The caller has been released. |
498 | 16200001 | The caller has been released. |
577 | 16200001 | The caller has been released. |
646 | 16200001 | The caller has been released. |
712 | 16200001 | The caller has been released. |
786 | 16200001 | The caller has been released. |
[all …]
|
| /ohos5.0/docs/en/release-notes/release-definitions/ |
| H A D | Release-version-definitions.md | 14 …led, built, and tested in a centralized manner, and finally reviewed and released by the community.
18 …ranch released in the OpenHarmony community. This branch is compiled, built, and tested in a centr…
36 …the maintenance schedule of the LTS and Release branches that have been released in the OpenHarmon…
|
| /ohos5.0/docs/zh-cn/application-dev/media/audio/ |
| H A D | audio-call-development.md | 138 console.info('Renderer already released');
143 console.info('Renderer released');
263 console.info('Capturer already released');
268 console.info('Capturer released');
|
| H A D | using-audiorenderer-for-playback.md | 27 - released状态： 在prepared、paused、stopped等状态，用户均可通过[release()](../../reference/apis-audio-kit/js-apis-…
189 console.info('Renderer released.');
335 // 渲染器状态不是released状态，才能release
337 console.info('Renderer already released');
|
| /ohos5.0/docs/en/application-dev/media/audio/ |
| H A D | audio-call-development.md | 136 // The AudioRenderer can be released only when it is not in the STATE_RELEASED state.
138 console.info('Renderer already released');
143 console.info('Renderer released');
261 … // The AudioCapturer can be released only when it is not in the STATE_RELEASED or STATE_NEW state.
263 console.info('Capturer already released');
268 console.info('Capturer released');
|
| /ohos5.0/drivers/hdf_core/framework/support/platform/src/fwk/ |
| H A D | platform_device.c | 123 if ((ret = OsalSemInit(&device->released, 0)) != HDF_SUCCESS) { in PlatformDeviceInit()
129 (void)OsalSemDestroy(&device->released); in PlatformDeviceInit()
148 (void)OsalSemDestroy(&device->released); in PlatformDeviceUninit()
|
| /ohos5.0/docs/en/application-dev/reference/apis-drm-kit/ |
| H A D | errorcode-drm.md | 76 Invalid **MediaKeySystem** instances are not released in time.
94 Invalid **MediaKeySession** instances are not released in time.
|
| /ohos5.0/docs/en/application-dev/napi/ |
| H A D | use-napi-faqs.md | 86 …released unexpectedly. When all the **tsfn** calls are complete, **napi_release_threadsafe_functio…
88 …to ensure that **tsfn** is not held or used by **env** after **env** is released. If **env** conti…
169 // Callback to be invoked when tsfn is released.
172 OH_LOG_INFO(LOG_APP, "tsfn is released");
176 OH_LOG_INFO(LOG_APP, "ctx is released");
221 … // When the asynchronous operation is complete, tsfn has been released and set to nullptr.
279 3. If **env** is not a valid **napi_env** (for example, a released **env**), **napi_generic_failure…
|
| /ohos5.0/docs/en/release-notes/changelogs/OpenHarmony_4.0.3.2/ |
| H A D | changelog-security.md | 8 For the released JavaScript APIs that use **ParamsSpec** and its child classes **IvParamsSpec**, **…
66 Behavior of released JavaScript APIs will be changed.
|
| /ohos5.0/foundation/arkui/ui_lite/frameworks/themes/ |
| H A D | theme.cpp | 39 buttonStyle_.released = StyleDefault::GetButtonReleasedStyle(); in InitButtonStyle()
|