5 ms·
I don't think that's really fair, the largest Chrome task in memory isn't a tab or extension. Yes I suppose it isn't perfectly isolated and if something happens
by muze 12y ago
I don't think that's really fair, the largest Chrome task in memory isn't a tab or extension. Yes I suppose it isn't perfectly isolated and if something happens to the main program task it will obviously cause problems but if a single page or extension crashes everything else lives on.
- yellowapple 12y agoIt's a perfectly fair point. The fact that the largest Chrome task by far is not a tab or extension at all, but is the core of Chrome itself, indicates that maybe - just maybe - Chrome isn't doing as good a job of keeping things isolated as it should. That process shouldn't be doing a whole lot beyond driving the UI and managing the lifecycles of its children.
- frankzinger 12y agoThe point is to isolate any code which renders HTML, plugins, etc., i.e., anything which processes untrusted external input, something which the main process does not do.