The JVM allocates invalid memory sizes that causes leaks. Firefox and chrome are probably accessing the same memory addresses that the JVM thinks it has access to but doesn't. I see the same problem when I run Starcraft 2 and a high-resource consuming java app.
-- Todd Millecam /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
