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
Apparently at random (maybe 1/10 times?), when you close the tab (not not when you navigate away?) there is a memory leak which leaves references to elements on the now unloaded DOM in memory, and as a result the gc does not destroy all the JS objects correctly. Symptoms experienced so far are:
after a while, new tabs fail to initialise the application at all
There is a residual error with the shutdown procedure resulting from the recent refactoring in [cv-pls], for which I will commit a fix shortly, but I'm creating this issue and leaving it open as I am not 100% sure this will fix the problem, due to it's apparent randomness.
The text was updated successfully, but these errors were encountered:
Apparently at random (maybe 1/10 times?), when you close the tab (not not when you navigate away?) there is a memory leak which leaves references to elements on the now unloaded DOM in memory, and as a result the gc does not destroy all the JS objects correctly. Symptoms experienced so far are:
There is a residual error with the shutdown procedure resulting from the recent refactoring in [cv-pls], for which I will commit a fix shortly, but I'm creating this issue and leaving it open as I am not 100% sure this will fix the problem, due to it's apparent randomness.
The text was updated successfully, but these errors were encountered: