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
There are a handful of spots in Kibana where unresolved promises are used to stop the execution chain. The concern is that these promises are never garbage collected, so they present a memory leak issue.
In #3014, Promise.halt() was introduced, which will simply keep a single unresolved promise around, which will be the only promise that isn't garbage collected. Since then and catch are overridden in this new promise, the chain should not build up, and old parts of the chain should be garbage collected.
tl;dr unused, unresolved promises should be replaced with Promise.halt.
The text was updated successfully, but these errors were encountered:
It looks to me that this issue is outdated, since we are trying to move nowadays to Vanilla JS promises, and not have any tight to a specific (e.g. Angular) implementation of promises.
I'll close this, but feel free to reopen, if it is still relevant.
There are a handful of spots in Kibana where unresolved promises are used to stop the execution chain. The concern is that these promises are never garbage collected, so they present a memory leak issue.
In #3014,
Promise.halt()
was introduced, which will simply keep a single unresolved promise around, which will be the only promise that isn't garbage collected. Sincethen
andcatch
are overridden in this new promise, the chain should not build up, and old parts of the chain should be garbage collected.tl;dr unused, unresolved promises should be replaced with Promise.halt.
The text was updated successfully, but these errors were encountered: