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
The default printer for JS targets (ConsoleView) leaks memory in the background (Tested in the latest Chrome, Firefox and Safari) (Interestingly IE 11 seems to be unaffected).
Basically the ConsoleView creates (but does not add to the document) DOM elements for all logged messages regardless of weather the printer has been "attached" and visible on screen. Because the printer is added to the Console by default, but not attached, it silently logs and creates DOM elements to the point of causing memory issues.
Because it creates DOM elements the chrome debugger doesn't show it as a javascript memory leak(!) (But pressing shift-escape and viewing the chrome task manager (or even the using your system task manager) will show the issue).
To fix the issue, it is as simple as "Console.removePrinter(Console.defaultPrinter)" but I'm still raising the issue as this issue is present by default and so will cause memory leaks by default
The text was updated successfully, but these errors were encountered:
The default printer for JS targets (ConsoleView) leaks memory in the background (Tested in the latest Chrome, Firefox and Safari) (Interestingly IE 11 seems to be unaffected).
Basically the ConsoleView creates (but does not add to the document) DOM elements for all logged messages regardless of weather the printer has been "attached" and visible on screen. Because the printer is added to the Console by default, but not attached, it silently logs and creates DOM elements to the point of causing memory issues.
Because it creates DOM elements the chrome debugger doesn't show it as a javascript memory leak(!) (But pressing shift-escape and viewing the chrome task manager (or even the using your system task manager) will show the issue).
To fix the issue, it is as simple as "Console.removePrinter(Console.defaultPrinter)" but I'm still raising the issue as this issue is present by default and so will cause memory leaks by default
The text was updated successfully, but these errors were encountered: