If you are using Windows 10 build 10525 and were using Google Chrome beta browser with 64-bit support, the company is one-step closer to a release. Within the last few hours, the Chrome team has pushed an update to the Canary channel. The update adds "support for int 2e fallback system call stub in Win10 " and fixes the crashes.

For those who do not know, Chrome Canary is the nightly build channel for the Google Chrome browser. As such, it cannot be installed as a default browser and in fact, installs alongside a public or beta build of Chrome on your system. Although the browser works just fine, due to its frequent experimental nature, it is not recommended for daily use (having said that I do use it for that and have for a long time).

Starting with Windows 10 build 10525 for Insider the 64-bit versions of Chrome were crashing (Beta and Canary). The fault is with Google as they were using unauthorized 'hooking' to work around Microsoft's APIs. Evidently, Microsoft's tools for 64-bit systems costs (no joke) $9,995 and Google opted to work around instead of paying up. Microsoft changed how memory is handled in this build and it broke Google's hack. You can read more from Windows Central member nohone, who left some detailed comments about the bug here.

The good news today is the fix is working in Chrome Canary 46.0.2489.0 (64-bit), and you can see the commit right here. The next step, after further testing and feedback, is to push it up to the Chrome beta channel, where the 64-bit version of the browser is at right now. This process could be just a few days or a week or more as beta builds are not as frequent as Canary ones. We'll, of course, keep you posted of when that happens.

For now, if you are using the Chrome beta 64-bit on Widows 10 10525, you can still use the –no-sandbox flag to get around the hooking issue.

Source: Google