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
JSVM now initialized ONLY if API actually uses middleware or virtual endpoint.
Additionally HTTP client which is used to communicate with the dashboard gets re-used for all connections.
Fix#2752Fix#2702
JSVM now initialized ONLY if API actually uses middleware or virtual endpoint.
Additionally HTTP client which is used to communicate with the dashboard gets re-used for all connections.
Fix#2752Fix#2702
(cherry picked from commit d129c5e)
Branch/Environment/Version
Describe the bug
Enable JSVM consumes a lot of memory
Reproduction steps
Actual behavior
The registration API calls jsvm.init, whether or not the API use js
Expected behavior
When register the compose API calls jsvm.init
code
The API type is not determined before calling spec.jsvm.init
Memory usage is as follows
The text was updated successfully, but these errors were encountered: