1e41f4b71Sopenharmony_ci# Ability Subsystem Changelog 2e41f4b71Sopenharmony_ci 3e41f4b71Sopenharmony_ci## cl.ability.1 Added a Restriction to childProcessManager to Limit the Maximum Number of Child Processes Allowed 4e41f4b71Sopenharmony_ci 5e41f4b71Sopenharmony_ci**Access Level** 6e41f4b71Sopenharmony_ci 7e41f4b71Sopenharmony_ciPublic API 8e41f4b71Sopenharmony_ci 9e41f4b71Sopenharmony_ci**Reason for Change** 10e41f4b71Sopenharmony_ci 11e41f4b71Sopenharmony_ciThere is a potential risk of malicious calls when applications can initiate an unlimited number of child processes, so it is necessary to set a restriction on the number of child processes allowed. 12e41f4b71Sopenharmony_ci 13e41f4b71Sopenharmony_ci**Change Impact** 14e41f4b71Sopenharmony_ci 15e41f4b71Sopenharmony_ciThis change is a non-compatible change. 16e41f4b71Sopenharmony_ci 17e41f4b71Sopenharmony_ciBefore change: The total number of child processes that can be started by an application through **childProcessManager** is not limited. 18e41f4b71Sopenharmony_ci 19e41f4b71Sopenharmony_ciAfter change: An application can start a maximum of 512 child processes through **childProcessManager** (non-SELF_FORK mode). 20e41f4b71Sopenharmony_ci 21e41f4b71Sopenharmony_ci**Start API Level** 22e41f4b71Sopenharmony_ci 23e41f4b71Sopenharmony_ci11 24e41f4b71Sopenharmony_ci 25e41f4b71Sopenharmony_ci**Change Since** 26e41f4b71Sopenharmony_ci 27e41f4b71Sopenharmony_ciOpenHarmony SDK 5.0.1.1 28e41f4b71Sopenharmony_ci 29e41f4b71Sopenharmony_ci**Key API/Component Changes** 30e41f4b71Sopenharmony_ci 31e41f4b71Sopenharmony_ci**startChildProcess** (non-SELF_FORK mode) and **startArkChildProcess** in **childProcessManager** 32e41f4b71Sopenharmony_ci 33e41f4b71Sopenharmony_ci**Adaptation Guide** 34e41f4b71Sopenharmony_ci 35e41f4b71Sopenharmony_ciNo adaptation is required. An application can start a maximum of 512 child processes through **childProcessManager**. When the maximum number is reached, no more child processes can be started. 36