Microsoft has pulled the Microsoft Edge 122.0.2365.63 replace after customers reported receiving “Out of reminiscence” errors when searching the online or accessing the browser settings.
Microsoft released Edge 122.0.2365.63 yesterday, and shortly after, customers started reporting throughout a number of websites that the browser was crashing repeatedly with reminiscence errors.
BleepingComputer was first alerted to the difficulty yesterday by one in all our readers, who mentioned the issue affected Home windows 10 and Home windows 11 customers.
Since then, the bug has been broadly reported, with customers receiving “This web page is having an issue” or “Not sufficient reminiscence to open this web page” errors whereas searching the online, with an error code of “Out of Reminiscence.”
“I simply up to date to 122.0.2365.63 (Official construct) (64-bit) and instantly nothing masses. I simply get the 2 errors “this web page is having an issue” and “not sufficient reminiscence to open this web page” on any web page, together with the brand new tab web page and settings. Anybody else have the identical drawback?,” reads a post on Reddit.
Supply: Reddit
It was later decided that the Enhanced Internet Safety characteristic was accountable when customers had it configured to ‘Strict’ safety. This characteristic might be managed by going to Settings > Privateness, search, and providers and scrolling right down to ‘Improve your safety on the internet‘ beneath Safety.
After decreasing the setting to ‘Primary’ or disabling the ‘Improve your safety on the internet’ characteristic altogether, the bug could be fastened, and customers might browse the online usually.
Nevertheless, a few of these affected can not entry the Settings web page to show this characteristic off as they obtain the Out of Reminiscence error as an alternative.
Since then, Microsoft has pulled the Edge 122.0.2365.63 replace, with the most recent model now 122.0.2365.59.
This launch will not be the primary time this bug has popped up, with Microsoft Edge Canary customers reporting the issue in current builds. Microsoft lastly fastened the bug in Canary 124.0.2434.0, launched yesterday, however seems to have forgotten to forestall the bug from making it into the Secure channel.
