Re:Google Modifies HTTP, Makes Chrome 50% Faster
by omellet on Monday April 11, 2011 @08:18AM
(#2432291)
Try adding --disable-internal-flash to your chrome shortcut, it'll use regular flash instead of the sandboxed version.
Re:Google Modifies HTTP, Makes Chrome 50% Faster
by pilif on Monday April 11, 2011 @08:34AM
(#2432317)
actually, I would believe the sandbox was added to prevent flash from accessing parts of your machine that it shouldn't be able to access.
This is not about preventing Flash from crashing, but about preventing your machine from getting owned by an exploit for one of the countless discovered and unpatched flash security flaws.
Re:Google Modifies HTTP, Makes Chrome 50% Faster
by nddrylliog on Monday April 11, 2011 @07:41AM
(#2432216)
> Sometimes I think Google needs a bigger QA team
That's an understatement :)
When I visited Google Zürich (admittedly not as crucial as Mountainview) I learned that unit testing was mostly used so they had pretty red/green lines on those LCD screens in the hall, and that any dev could break the version /in production/ pretty easily with a misplaced commit...
What seems rather ironical is that I only started having these issues with Chrome after they added the Flash-sandbox, which was supposedly made to stop Flash from crashing the browser. With the result that Flash is always crashing the browser, something it never did before.
Sometimes I think Google needs a bigger QA-team.