Yeah, this is an unavoidable consequence of their (current) 1-process model for tabs. They have a system for running tabs in a process separate from the browser

Yeah, this is an unavoidable consequence of their (current) 1-process model for tabs. They have a system for running tabs in a process separate from the browser, but they don't currently split tabs out into multiple processes, so you can get lag on switching tabs. IIRC they are working on expanding this so that tabs are split across multiple processes, without using Chrome's resource-hungry Process Per Tab approach.