Maybe you're right about lowest memory consumption, but what keeps me going back to Chrome is consistency in good performance and the fact that I can easily shut down one tab without having to restart the whole browser to reduce memory if that ever happens.
All browsers do have memory leaks but the fact that FF's memory continually increases to the point where I have to restart the whole browser every day is mentally tiring. This is where Chrome just got it right.
This was fixed for extension-free firefox. Today this is fixed, for extensions as well.
What was happening was that extensions had references to dom-nodes of a page, that prevented the page from being unloaded when you close the tab. Unless of course, the extendion author bothered to fix this from their side. Now, an extension has essentially "weak references" to dom nodes. (think: symlink)
I second this. On Ubuntu 12.04 Unity crashes after approximately 20 days of uptime and that's Almost the only time I restart Firefox. I regularly have a single session open for weeks.
Just to update, after a couple of hours playing with it, I am finally noticing it fluxuates up and down. It appears to let go of consumed memory after a period of inactivity. That's great news!
Glad to hear it! But as implied above, memory consumption is only interesting because of its effects on performance and stability (both of the browser and other programs running on the system). Don't choose your browser by looking at the memory consumption, choose your browser based on how it feels when you use it.
All browsers do have memory leaks but the fact that FF's memory continually increases to the point where I have to restart the whole browser every day is mentally tiring. This is where Chrome just got it right.