You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In the recent versions of v8 the callback we use for garbage collection is called multiple times (much more than in previous versions). During the callback execution the whole object tree is checked for links to the objects marked for release, which blocks the app. For huge apps this check may take a lot of time, during which the app freezes. As the callback is now executed much more often, some apps become unusable.
Describe the solution you'd like
The idea is to execute in the same way as we have done for webpack in 5.4 – prompt the users, who do not have set markingMode in the app/package.json. Explain them that currently they are using the markingMode: full version that is deprecated and will be removed in 7.0.0 release. Ask them if they want to use the markingMode: none, which will be the only one in 7.0.0 release or they want to keep using the markingMode: full. Persist the answer in the app/package.json file (i.e. set the value of markingMode in the app/package.json).
In consecutive commands in the same project, in case markingMode: full is set in the package.json, show a huge warning that this markingMode is deprecated and in 7.0.0 it will be removed. Ask the user to log a new issue in Android runtime repo with more details why the markingMode: full is set.
NOTE: In non-interactive terminals, in case the markingMode is not set in app/package.json, consider it as set to markingMode: full, i.e. show the warning.
Describe alternatives you've considered
Find out how to lower the calls to the garbage collection callback.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
In the recent versions of v8 the callback we use for garbage collection is called multiple times (much more than in previous versions). During the callback execution the whole object tree is checked for links to the objects marked for release, which blocks the app. For huge apps this check may take a lot of time, during which the app freezes. As the callback is now executed much more often, some apps become unusable.
Describe the solution you'd like
The idea is to execute in the same way as we have done for webpack in 5.4 – prompt the users, who do not have set markingMode in the app/package.json. Explain them that currently they are using the markingMode: full version that is deprecated and will be removed in 7.0.0 release. Ask them if they want to use the markingMode: none, which will be the only one in 7.0.0 release or they want to keep using the markingMode: full. Persist the answer in the app/package.json file (i.e. set the value of markingMode in the app/package.json).
In consecutive commands in the same project, in case markingMode: full is set in the package.json, show a huge warning that this markingMode is deprecated and in 7.0.0 it will be removed. Ask the user to log a new issue in Android runtime repo with more details why the markingMode: full is set.
NOTE: In non-interactive terminals, in case the markingMode is not set in app/package.json, consider it as set to markingMode: full, i.e. show the warning.
Describe alternatives you've considered
Find out how to lower the calls to the garbage collection callback.
The text was updated successfully, but these errors were encountered: