# Edge Browser back working again.... again

**URL:** <https://boards.straightdope.com/t/edge-browser-back-working-again-again/916435>\
**Category:** About This Message Board\
**Created:** [July 27, 2020, 1:14am UTC](https://boards.straightdope.com/t/edge-browser-back-working-again-again/916435 "2020-07-27T01:14:50Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Melbourne](https://avatars.discourse-cdn.com/v4/letter/m/b5e925/32.png) [@Melbourne](https://boards.straightdope.com/u/Melbourne)\
**Post date:** [July 27, 2020, 1:14am UTC](https://boards.straightdope.com/t/edge-browser-back-working-again-again/916435/1 "2020-07-27T01:14:50Z")

</div>

Just updated to 86.0.587.0 (Official build) canary 32 bit.  
Which is good, because 86.0.586.0 (running on Win7-32) always crashed on this site when I scrolled down far enough to see the first advertisement.

Edge has been having this kind of problem for a while – I see complaints going back several years – and I’ve previously mentioned 85.0.478.44 on Win7-64.

---

<div class="post-metadata">

**Author:** ![Terminus\_Est](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/terminus_est/32/3087_2.png) [@Terminus\_Est](https://boards.straightdope.com/u/Terminus_Est)\
**Post date:** [July 27, 2020, 1:54am UTC](https://boards.straightdope.com/t/edge-browser-back-working-again-again/916435/2 "2020-07-27T01:54:07Z")

</div>

Edge is based on Chromium now, the same as Google Chrome. So if it works on Chrome, it should work on Edge.

---

<div class="post-metadata">

**Author:** ![Melbourne](https://avatars.discourse-cdn.com/v4/letter/m/b5e925/32.png) [@Melbourne](https://boards.straightdope.com/u/Melbourne)\
**Post date:** [July 27, 2020, 4:16am UTC](https://boards.straightdope.com/t/edge-browser-back-working-again-again/916435/3 "2020-07-27T04:16:42Z")

</div>

They are both based on Chromium, and so both use the same rendering engine, so pages should display the same in both Edge and Chrome. But they aren’t the same, have different features, handle errors differently, and have different bugs.

---

<div class="post-metadata">

**Author:** ![GreenWyvern](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/greenwyvern/32/2834_2.png) [@GreenWyvern](https://boards.straightdope.com/u/GreenWyvern)\
**Post date:** [July 27, 2020, 7:48am UTC](https://boards.straightdope.com/t/edge-browser-back-working-again-again/916435/4 "2020-07-27T07:48:16Z")

</div>

I switched to [Slimjet](https://www.slimjet.com/) a few months ago, and I’m very happy with it.

It’s also a Chromium-based browser, but faster and smaller, with many improvements like built-in ad-blocking, privacy, and anti-tracking. It has many useful extra features and customization options, and it can use Chrome extensions and themes.

I haven’t had any problems on this site with it.

---

<div class="post-metadata">

**Author:** ![Steven\_G](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/steven_g/32/5080_2.png) [@Steven\_G](https://boards.straightdope.com/u/Steven_G)\
**Post date:** [July 27, 2020, 4:04pm UTC](https://boards.straightdope.com/t/edge-browser-back-working-again-again/916435/5 "2020-07-27T16:04:41Z")

</div>

Odd, never had any issues with the “old” Edge on the SDMB old site. Jumped to the new Chromium version, and it worked there and also here on the new site without issues.

The fact you are on Win-7 should not make any difference, but my experience is all on Win-10

HAve yu got any add-ins or extensions that might cause the problem? When you say “crashed”, what exactly happens?

---

<div class="post-metadata">

**Author:** ![Melbourne](https://avatars.discourse-cdn.com/v4/letter/m/b5e925/32.png) [@Melbourne](https://boards.straightdope.com/u/Melbourne)\
**Post date:** [July 28, 2020, 1:10am UTC](https://boards.straightdope.com/t/edge-browser-back-working-again-again/916435/6 "2020-07-28T01:10:09Z")

</div>

Edge shuts down whenever it detects any kind of problem. It just shuts  
down. (By way of comparison: FF stops responding for long periods, IE  
would shut down just the individual process (the individual page).

Although there have been similar problems with Edge and some of the  
API’s used by advertising for several years, my problems were both  
with specific individual builds: I got an update, I had shutdowns  
until I got the next update.
