Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 86b15017 authored by Martijn Coenen's avatar Martijn Coenen
Browse files

Update documentation on AppZygote limits.

Bug: 146482195
Test: N/A
Change-Id: I8608824af708f5eab60b49daad804ead4c927599
parent fe62705a
Loading
Loading
Loading
Loading
+6 −1
Original line number Diff line number Diff line
@@ -2976,7 +2976,12 @@
             depends on the number of isolated services that an application starts,
             and how much memory those services save by preloading and sharing memory with
             the app zygote. Therefore, it is recommended to measure memory usage under
             typical workloads to determine whether it makes sense to use this flag. -->
             typical workloads to determine whether it makes sense to use this flag.

             <p>There is a limit to the number of isolated services that can be spawned from
                the Application Zygote; the absolute limit is 100, but due to potential
                delays in service process cleanup, a much safer limit to use in practice is 50.
             -->
        <attr name="useAppZygote" format="boolean" />
        <!-- If this is a foreground service, specify its category. -->
        <attr name="foregroundServiceType" />