SOLVED

Cache Bug in Edge Version 95.0.1020.53

Brass Contributor

Since we have updated to 95.0.1020.53 (from .44), we are dealing with a very hard to explain bug, which I can only refer to as a cache bug, causing Edge to double-up on JavaScript Get requests and therefore providing duplicate results or erroring out  a webpage. The bug goes away by using any of the 2 following methods, which to me indicates this is some sort of cache bug.

 

1. Open a InPrivate Window and visit the problematic website, now Edge performs as expected.

2. Clear the cache, go into Developer Mode (F12), go to Network and select Disable Cache, visit the problematic website, now Edge performs as expected. 

 

Attached is a photo of the RBC website trying to perform a transfer. The error goes away using any of the 2 methods above. Hopefully someone can help or fix this bug.

 

Bank.jpg

3 Replies

@GreatToHearFromYou Hi!  This does sound like an odd bug!  In this case it might be best to reach out to Support (https://microsoftedgesupport.microsoft.com/hc/en-us).  Since it seems a little hard to explain/reproduce, they would be able to work with you directly to investigate.  

 

Or if anyone else has fixed a similar issue, feel free to comment! 

 

-Kelly

best response confirmed by GreatToHearFromYou (Brass Contributor)
Solution

@Kelly_Y
Thank you for your quick response, much appreciated! Because I could not find any other reports about this bug, I decided to go with the process of elimination and found that it was one of the extensions we use causing this bug. We have disabled the extension now and Edge is back behaving as expected.

@GreatToHearFromYou Awesome!  Happy to hear everything is back to working as expected! 

 

-Kelly

1 best response

Accepted Solutions
best response confirmed by GreatToHearFromYou (Brass Contributor)
Solution

@Kelly_Y
Thank you for your quick response, much appreciated! Because I could not find any other reports about this bug, I decided to go with the process of elimination and found that it was one of the extensions we use causing this bug. We have disabled the extension now and Edge is back behaving as expected.

View solution in original post