Neither, as I am only looking at private memory, which is by definition not shar...

		kmm on Jan 28, 2012 \| parent \| context \| favorite \| on: Tell HN: RAM Requirements are going through the ro... Neither, as I am only looking at private memory, which is by definition not shared. Interestingly, most of my extensions have 0K shared memory, which implies they're all keeping their own version of JavaScript libraries in their own memory space. That might explain most of the problem. It doesn't seem easy to solve a problem like this, without reinventing the shared library and the accompanying "DLL hell".

And in fact the memory isolation between javascript execution contexts is one of Chrome's most touted security features.