4 ms·
Chrome Sync is, AFAIK, not a push service. Something polled a Google server, it returned a bad answer, it crashed the browser. Why is this important? Because
by DannyBee 14y ago
Chrome Sync is, AFAIK, not a push service.
Something polled a Google server, it returned a bad answer, it crashed the browser.
Why is this important?
Because it's entirely possible that Firefox or Safari, for example, could have been crashed by contacting the safebrowsing server, and the safebrowsing server returning an answer that crashes it.
Firefox also does remote firefox update checks and plugin update checks, etc.
None of the browsers you mention are "independent" of internet servers anymore. They are meant to function independently, as is Chrome, but exactly the right remote bug could likely crash all of them.
- andyzweb 14y agoI have safebrowsing and auto update disabled since FF3.6
- lmkg 14y agoWhy is it possible to receive a response that crashes the browser? I'll allow (with reservations) your premise that browsers aren't so independent anymore. But it seems to me that input from an external source (even trusted) ought to be validated, and malformed input should raise a warning or something. The fact that crashing is a possible behavior upon receiving unexpected input is surprising to me.
- polyfractal 14y agoWell that's the point of a bug, isn't it? Chrome didn't handle malformed input appropriately and crashed because of it. It wasn't a command that shut down Chrome, it was just poor handling of an edge-case which resulted in unexpected behavior (crash). It's a sad truth that most programs will explode if you fling garbage at them. When push comes to shove, many development timelines don't have room to bulletproof against everything
- deelowe 14y agoWhy is it possible to gain admin access to an operating system by sending requests that crash the web server? Bugs happen.