Now Reading
Google Chrome will no longer crash on Windows 10 Build 10525
0

Google Chrome will no longer crash on Windows 10 Build 10525

by AshwinAugust 28, 2015

Windows 10 Build 10525, which was released a week ago, brought in a fantastic bug, which crashed Google Chrome on launch.

Google-Chrome-64-bit

Now that we have that sarcasm out of the way, let me recap on what happened later.

Users were quick to blame Microsoft for the issue, and began demanding a Windows Update to fix the problem. This was due to the fact that Windows 10 Build 10525, brought in a massive change to the way how the operating system handles the memory. The new addition to the Memory Manager, is called compression store. This is believed to have affected the way how Chrome worked on 64-build architecture.

But soon, a thread was spotted at the Google Product forums where many users said, that it was a problem in Google’s browser itself.

The Mountain View company’s developers, officially acknowledged the issue, and narrowed it down to the Google Chrome 64 bit version. Two workarounds, one of which is not actually recommended, were also found.

  • The first one is to uninstall Chrome 64-bit, and switch to Chrome 32-bit or Google Chrome Canary channel.
  • The second one, is to disable the Sandbox. which puts the browser at risk, and as such not advisable.

Today, Microsoft released Windows 10 Build 10532, and the release notes for which flags “Google Chrome not working in Preview Build”, as a known issue. It also highlighted the aforementioned workarounds, and said that Google is working on the issue.

But it appears that, Google is one step ahead, and has in fact rolled out an update to fix the issue. Sadly, it isn’t the stable channel of Chrome which has been updated to fix the crash issues. Windows Central reports that Google Chrome beta version 45.0.2454.78 is the one which works on Build 10525 and above.

The current stable version of Google Chrome 64-bit is Version 44.0.2403.157 m (64-bit). So, it may not be long until v45 is rolled out to the general public.

A Chrome engineer explained on the Chromium bug tracker website, that Chrome’s sandboxed processes uses 64-bit syscall stub validation, to check which third-party software try to hook inside. 32-bit versions of the browser work differently, and are affected by third party software which break the browser’s stability, and cause leaks and crashes in the sandboxed process.

Basically, the statement claims that 64-bit version is more secure. than the 32-bit one, thanks to the advanced security features in the architecture.

Google has now officially closed the issue tracker for the bug which caused the crash in Build 10525.

Leave a Response