Google Chrome Resource Hungry from Startup

Here is something I bet not many have noticed. On startup not only does Chrome start, it starts with a lot of RAM in use. While there are the idjuts that like to call anyone RAM-conscious idjuts who don’t get what RAM for and say that unused RAM is wasted RAM, the point of being RAM conscious is that, just perhaps, maybe, you want to use your hyper-powered modern computer to do more than three tasks at a time, and maybe a program won’t release the RAM some thread or process it generated was using after the fact for all sorts of reasons, like forking Firefox and rushing into implementation when some really good architects warned that the technology and understanding for multi-process browsing is not really mature, trustworthy, or…implemented in any satisfactory manner. Hmm…

The worst thing, though, is upon start-up I just watched these processes, and in RAM use every one of them just climbed and climbed and climbed. After a while 73,390 or so K for one process dropped back to about 70,880 but…