Linux client 1.16.0.5 revisiting memory lane

I hate to say it but 1.16.0.5 client for the linux-alpha is up to its old ways again I think. I really don’t fancy the memory leaks either but not sure if it’s just a matter of the ATI card now, or if it’s going back to its old ways. For an alpha, you would expect choppy and non-functioning clients but back in 1.13, it was running… VERY smoothly. Strangely enough, with each version upgrade, there came some memory leaks that kept coming and coming. You would launch the client, it’d be great for a little while, then suddenly would slow down and be seriously choppy. Being the only application running on a P4-1.5G ram machine dedicated strictly for testing, it’s hard to imagine what else could be doing this.

Well, then there was seriously rejoicing in the 1.15.02 and 03 versions. The leak was gone it seemed. There was much rejoicing…

But it doesn’t stop there! No, the leak just refuses to be shoved aside. No, it came back for a sequel. The brilliant 1.16.0.5 client has it again. Ick. Anyone else running into this issue? I seem to recall a forum post I started a while back in version 1.14 that spoke of this, but unsure if anyone has had the chance to encounter this beast. It doesn’t make it unplayable…. if you don’t mind choppy and laggy graphics. Nothing has really changed as far as X-server and fglrx driver versions so you want to seriously wonder what exactly is keeping it from working and why it’s been in alpha for so long. No wait, don’t answer that last one.

Seriously though. Has anyone else encountered this problem? I’m too lazy to fire up a debugger while the client is running to see what exactly the internals are doing that’s chewing up the resources.