Ive frequently been running in to some sites that have bad scripts that can use 100% of the CPU to the point the mouse can barely move.

How bout giving each tab its own thread and or setting controls so if a tab trays to consume to much CPU its execution is halted for a user decision.

I'm not sure but this might be more of a gecko thing.

Quote
eadthem
I'm not sure but this might be more of a gecko thing.

Yes, it is.

And usually these lockups aren't caused by scripts, but by Flash objects. Flashblock is your friend...

I frequently have these problems with flash block on. So that leaves HTML java script and java. java of corse displays a icon when it runs, so that leaves java script and HTML.

I still mantain that each tab shuld have its own thread so that if the tab is using to much resources the browser can halt it before it locks everything up to the point that even the cursor is slow when doing a end task on k meleon.

A multi-process architecture spawns multiple completely separate processes, with all of the overheads attached to each individual process.
Chrome's multi-process model is just an unnecessary ressource hog.
Multi-threading and multi-process plugins on the other hand would make sense.