Serve the attached testcase over a simple HTTP server Enter 5000 and 10000 and press enter. -> Note the time taken Now close the tab -> Note the time taken for the CPU to process the closing of tab (I am guessing as soon as the tab is closed, browser will cleanup any leftover strings). **5000** - Chrome: https://share.firefox.dev/41HJFoL (4.8s + 1 second approximate, not captured) - Nightly: https://share.firefox.dev/4blNu7a (19s + 4s) 10000 - Chrome: https://share.firefox.dev/3F1owOw (10s) - Nightly: https://share.firefox.dev/4hZPBAh (40s) - Nightly to clear data: https://share.firefox.dev/3XoYlHH (11s) Somewhat more concerning is that Firefox keeps the SSD in a constant 33% "active" state, which may mean more writes or more power use or both. Testcase generated by Chatgpt based on my prompts. Unrealistic testcase, but maybe it highlights some hotspots?
Bug 1951283 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Serve the attached testcase over a simple HTTP server Enter 5000 and 10000 and press enter. -> Note the time taken Now close the tab -> Note the time taken for the CPU to process the closing of tab (I am guessing as soon as the tab is closed, browser will cleanup any leftover strings). **5000** - Chrome: https://share.firefox.dev/41HJFoL (4.8s + 1 second approximate, not captured) - Nightly: https://share.firefox.dev/4blNu7a (19s + 4s) 10000 - Chrome: https://share.firefox.dev/3F1owOw (10s) - Nightly: https://share.firefox.dev/4hZPBAh (40s) - Nightly to clear data: https://share.firefox.dev/3XoYlHH (11s) Somewhat more concerning is that Firefox keeps the SSD in a constant 33% "active" state, which may mean more writes or more power use or both. Testcase generated by Chatgpt based on my prompts. Unrealistic testcase, but maybe it highlights some hotspots? (maybe we are more conservative than Chrome and flush to disk on every write?)
Open the attached testcase (OR download the testcase and Serve the attached testcase over a simple HTTP server) Enter 5000 and 10000 and press enter. -> Note the time taken Now close the tab -> Note the time taken for the CPU to process the closing of tab (I am guessing as soon as the tab is closed, browser will cleanup any leftover strings). **5000** - Chrome: https://share.firefox.dev/41HJFoL (4.8s + 1 second approximate, not captured) - Nightly: https://share.firefox.dev/4blNu7a (19s + 4s) 10000 - Chrome: https://share.firefox.dev/3F1owOw (10s) - Nightly: https://share.firefox.dev/4hZPBAh (40s) - Nightly to clear data: https://share.firefox.dev/3XoYlHH (11s) Somewhat more concerning is that Firefox keeps the SSD in a constant 33% "active" state, which may mean more writes or more power use or both. Testcase generated by Chatgpt based on my prompts. Unrealistic testcase, but maybe it highlights some hotspots? (maybe we are more conservative than Chrome and flush to disk on every write?)