Latest Editions of Windows 10 Break Chrome Browser

Reports that Windows 10 stops Google's Chrome browser from running appear to be only partially correct. While the problem does exist, it only affects people running test editions of Windows 10 which are not available to everyone.

The problem affects the version of Chrome designed for 64-bit PCs. If the problem strikes, the browser simply fails to show any page and instead displays the familiar "Aw Snap!" error message. It appears to affect all editions of 64-bit Chrome, from the standard edition through the various test editions, such as developer and Canary. (Source: computerworld.com)

Insider Preview Program Affected

Thankfully the problem isn't yet an issue for the standard version of Windows 10 that most people have downloaded. Instead it only affects those users who joined the Windows Insider program to test Windows 10 before it was released.

The Windows 10 Insider program is still in operation, meaning those users get to test out updates to Windows 10 before they are released to the general public. Members of the program can choose from several options for how quickly they get these updates: the earlier they get them, the less widely tested they are.

The Chrome problem appears to affect only those on the "fast ring" option, which downloads and installs the very latest test updates of Windows 10.

Memory Conflict The Likely Fault

The problem appears to be related to Chrome's use of sandboxing. That's a key security technique that involves putting each webpage into a walled off area within the computer's memory. The idea is that if any page turns out to house malicious software, it's unable to access and infect any of the computer's resources.

It seems that Microsoft has changed the way Windows handles memory in the latest test edition of Windows 10, using a technique designed to keep the computer running smoothly and quickly even when it has a lot to do. That seems to be conflicting with the sandboxing in Chrome to cause the crashes.

Some users report that disabling the sandboxing feature allows Chrome to run again. However, that's a temporary fix at best, as it drastically undermines the browser's security benefits. (Source: neowin.net)

What's Your Opinion?

Is it a concern that Windows 10 may be conflicting with a major rival firm's browser? Is it instead a sign that the testing program is working as intended by revealing such problems before the general public is affected? Should Microsoft work more closely with rivals such as Google to make sure their software works together smoothly?