Forum Discussion
Dev channel update to 87.0.637.0 is live
sid9-3 this might not be intentional, so we should figure out if it is or not. First, do you have anything listed in edge://crashes? If a tab crashes, it will have to reload. Next, are you closing Edge at all when you see this happen? When Edge re-opens with previous pages, it sometimes doesn't load all of the pages until you click on them, which may also appear as if they're reloading. One other possibility is that your machine is very low on memory, in which case Chromium-based browsers automatically unload tabs in order to free up space.
The only way for this to be intentional that I can think of is if you're the lucky recipient of a feature we're testing to unload not-recently used pages in order to reduce memory and battery usage. However, I don't believe we've actually started rolling this out yet, so the only way that would happen is if you've manually enabled it by turning on the flag. You'd know if you were using this feature if you see tab titles fading a while after you've left them untouched.
Hey josh_bodner thanks for the attention.
When I use Firefox it never autoloads, it's responsive while switching between tabs but use lots of resources. On the contrary Chromium (my primary browser) is efficient but not agile while opening/switching between tabs/new tabs after some time.
From your point I suppose autoloading is due to low memory availability.
But make it instantaneous while opening new tab.
sid9-3 Ah okay, you're comparing to a non-Chromium based browser, that's good to know. Firefox is actually really interesting since they have a completely different process model. In them, every tab is in the same process, so they can't shut down or pause the processes the same way we can when you switch tabs. That very likely contributes to the snappy switching you're used to: https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Multiprocess_Firefox
josh_bodner That's interesting.
Bdw the ''sleeping tab'' feature you mentioned is interesting. What I understood from my limited interaction with it is, it will enable the user to personalise resource usage and when a tab/site reloads. So a balance between efficiency and performance, right?
-Smooth scrolling (of course it's in the pipeline) should be the priority as it makes the overall experience smooth.
-The icons in the Edge UI needs fluent touch. In your presentations they look very smooth, a bit thick (I'm failing here to mention the particular design language for the word ''thick''), soft and textured. Currently I find the icons thin (again I hope you understand the difference between thick and thin in design language as I am no expert) and rough.
sid9-3 yes, the goal with sleeping tabs is for us to use as little memory as possible while still having no noticeable speed difference when doing things like switching between tabs. It's a tough tradeoff, since devices with different amounts of memory and users who use different amounts of tabs in different ways mean that there's not a "set" point that's perfect for every single user. That will also be why, once we start rolling out sleeping tabs, it will be very important for us to learn if there are any websites that don't respond well to being put to sleep (or more specifically, that don't wake up properly or are broken when they wake up), since we can also fine-tune our heuristics to learn what tabs not to put to sleep at all.