Windows 10 (Photo : Reuters)
Microsoft's Windows 10 release last July 2015 was largely successful but numerous hiccups were still encountered by users though not in the catastrophic magnitude. But it's a different story for Windows fans that opted to remain as Insiders. In their realm, problems and bugs are aplenty.
The latest trouble was brought about by the Windows 10 preview build 10525. It appears that the update suddenly crippled the popular Google Chrome browser and according to Computerworld, the problem specifically affects Windows Insiders using the 64-bit Windows 10 on their machines.
Following the jump to build 10525, 64-bit Chrome just experienced a meltdown. Firing up the browser will result to tabs just getting zapped which automatically generates the message "Aw Snap!" from Chrome. Then no pages will load.
The problem was due to the fact that 64-bit Chrome is incompatible with preview build 10525 of Windows, Computerworld added on its report, so the crashing is all but expected. Specifically, the built-in sandbox feature of the 64-bit Chrome appears to interfere with the Windows 10 beta architecture, the report said.
Sandbox is the anti-exploit Chrome feature that isolates its processes as protection against malware intrusion.
"It looks like the sandbox is breaking in the Win10 10525 previews for 64-bit Chrome," the Computerworld report quoted a Google engineer as saying.
As a quick fix, Windows Insiders are advised for now to switch to the 32-bit version that according to Google works just fine with Windows 10 - both the preview and public release. But those who insist in using Chrome in 64-bit flavor, the best solution available is to use the browser minus the sandbox feature.
Doing so, however, will open both the application and the operating system to possible attacks and Google, according to NeoWin, doesn't recommend the risky measure. It is best to stay on the safe zone in times like this.
While Google reassures that 64-bit Chrome going haywire in Windows 10 preview builds is but a "temporary breakage," the tech giant told NeoWin that users should "think twice before using builds from the Windows Insider Fast ring."
