Forum Discussion
josh_bodner
Microsoft
Nov 10, 2020Dev channel update to 88.0.692.0 is live
Hello Insiders! Today we’re releasing build 88.0.692.0 to the Dev channel. While there aren’t many product updates to mention this week, we do have some articles for you:
First, we’ve got ...
- Nov 13, 2020
Came for the Hololens 2 beta left with nothing? It was rumored around that Hololens 2 had a build but I'm not seeing anything?
BenR00002145
Nov 12, 2020Brass Contributor
josh_bodner Two things have changed on my computer: I have updated to this weekly dev channel update, and I updated Windows to 20H2.
I have many tabs that I keep open. Before the two things above, I could load edge (with all my ~100 tabs) and in a minute task manager would report that about 2-4 GB of memory are being used.
After the Tuesday updates, Task Manager now reports that edge is using, and I have double checked this, 19,633 MB (19 GB) That's with a G.
Something big happened. My first launch crashed because I was multitasking. Now that I'm not doing anything, Edge can load but it is sitting still at 19GB, still doing a lot of network traffic after about 5 minutes, and signifigant CPU usage (fluctuates up to 25% on an 8 core system).
Edit: 15 minutes later or so, and memory is at 15GB. I found that my "sleeping tabs" settings had changed to 1 hour (I had been aggressive with them at 15 minutes before, due to the way I use the browser). Changed the setting back to 15 minutes.
Also I need to understand a bit more about how the launch boost works, I wonder if that is triggering a different way for Edge to load, which is causing the massive memory, load time, and CPU usage.
- josh_bodnerNov 13, 2020
Microsoft
BenR00002145 I wouldn't think that the startup boost feature would result in this; all it does is pre-load certain Edge processes in memory when Windows starts up so that launching Edge the first time is faster. It shouldn't change anything about how tabs within Edge are restored or loaded.