Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Chrome's sandbox is not equivalent to having a separate jail for every web site. It is designed to prevent web content from attacking non-browser apps and data, not to prevent one web page from attacking another (though Chrome, like all browsers, has other mechanisms to do this).

Chrome does not guarantee one process per tab, or even per origin. If you reach its internal process limit -- or if a page does something like window.open() that gives it a reference to another tab -- then it will render multiple sites in the same processes, not sandboxed from each other: http://code.google.com/p/chromium/issues/detail?id=81877



Chrome is designed to guarantee that web content never cohabitates in a process with chrome:// URLs. Unfortunately, in this case that code was buggy.

There's nothing fundamentally different about Chrome's approach here than what you are advocating.

At some level, these policies have to be implemented with code, and that code can have bugs.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: