Memory overload with AMD Duron on 1.9

I have posted this as a bug, but it only seems to affect AMD Durons (with Athlon I am not sure, I only have 2 AMD Durons), which I did not know when I posted the bug.

This was the Bug Report: Your bug report regarding Bug: E1 V1.9.0.21 (DarkWood) Huge memory usage when visiting two locations in SL has been received, and assigned an ID of [rt.lindenlab.com #245184].

If I go to the locations secondlife://Simcoe/229/224 and then secondlife://DarkWood/107/38, in the Windows Native Client, or in the Linux Alpha Client, my memory usage goes up to over 800 MBytes. This means all memory is full, and SL is unusable

If I do the exact same thing on the exact same computers, but run SL using wine and the Windows Client, with exactly the same settings in Preferences, I get memory usage of 250 MBytes, which stays stable, and SL has a perfectly normal behaviour.

If I do this with the windows Native client, using my one-and-only Intel computer (Celeren 2.2 GHz, graphic card the same, as below), SL behaves perfectly normally, 250 odd MBytes memory used, and stays stable.

Is there something I must do on the client, to get it to run sanely on the AMD Duron chip? Or is this "expected behavior" ?

I would REALLY appreciate help on this - I have just ordered an AMD Athlon XP 3200+ to upgrade, but that will not help me if SL behaves likes this

And it is not windows or Linux, it seems to be the client itself.

I have asked around the Linux Alpha forum, and it seems this is a problem only I have.

So I guess I will have to live with it, until I find a solution myself.

If anyone has any hints on this, I would be grateful though

I'm runnin an AMD Athlon 2500+ and my memory usage gets up there too lately, don't know y but can't do much else nemore with sl running.

ive not tried it in linux (stupid netgear card) but with windows and a XP2200+ no unusual memory usuage, just likes to crash with alt tab

(altho not nearly as bad as it was when i was complaining about it)

In my case, my draw distance was 512, with reduce draw distance at 5 fps.

Up to 1.9, this seemed to be OK. After that, huge memory usage.

I am still confirming it with windows, but here are the results with linux when I set draw distance to 128: /263/a8/98735/1.html#post981165

What is still an issue is that memory usage of the client grows. But that may be because the memory is available.

I will update this post when I have tried it out on windows.

--- EDIT ---

Same in windows. After going to the two places that gave me problems, I get a memory usage of 370 MBytes. This is quite acceptable. So I guess I need to leave my draw distance at 128 or lower.

I also stopped getting the HUGE bad packets rate I had when I first arrived somewhere (more a linux phenomenon).

--- END EDIT ---