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
To limit browser resource consumption, it may be necessary to limit the total number of lines printed in the terminal area. This may be nice to have as an adjustable option.
The text was updated successfully, but these errors were encountered:
Do you have idea of how many lines it would take for things to become problematic? With browser tabs typically using tens of megabytes of RAM, it's hard to imagine even 100,000 lines of text making much a dent in that, but I really don't know how much overhead is involved with representing each HTML element in the browser.
Sometimes memory leaks can happen when jQuery tracks new elements that are added to the DOM. In any case, it would be best to run a test for several hours to see if we have any runaway effects.
After a 3h test, memory consumption increased from 75Kb (start) to 85Kb. Terminal contained 5300 lines at termination. At this time the memory footprint appears to be minimal, so this can remain as an enhancement (not a bug).
To limit browser resource consumption, it may be necessary to limit the total number of lines printed in the terminal area. This may be nice to have as an adjustable option.
The text was updated successfully, but these errors were encountered: