>>>>> "Michael" == Michael Milligan <email address hidden> writes:
Michael> Another data point. I'm having the same overall issue
Michael> using the radeonhd driver on my laptop, so there may or
Michael> may not really be an issue with leaks in the nvidia
Michael> driver. It sure seems to be related to firefox and flash
Michael> content as the memory usage of the xorg process ramps up
Michael> when I run firefox (1.5.x thru 3.0.5) and ramps up
Michael> exponentially faster for pages that have flash content.
Michael> Killing/quiting firefox frees up a lot of memory, but not
Michael> from Xorg's overall total. It has behaved like this (for
Michael> me) for the past couple of years. Only reason it's not a
Michael> big deal for me is I'm constantly having suspend/resume
Michael> issues since the 7.10 release, so uptime never exceeds a
Michael> couple of weeks anymore. :(
Hmm, thinking about this makes it pretty clear to me know. It really
must be firefox + flash. My firefox on x86 recently also acquired
about 1.5GB of RAM with the X server running at more than 2GB. Killing
the firefox instance also released quite a lot of RAM from the X
server. But more importantly: As reported earlier, I don't have the
problem on my amd64 desktop at work. And guess what! I don't have a
flash plugin running for my firefox there.
So please debugger folks. Test along these lines, and I am almost
certain you will find the real cause of this.
>>>>> "Michael" == Michael Milligan <email address hidden> writes:
Michael> Another data point. I'm having the same overall issue
Michael> using the radeonhd driver on my laptop, so there may or
Michael> may not really be an issue with leaks in the nvidia
Michael> driver. It sure seems to be related to firefox and flash
Michael> content as the memory usage of the xorg process ramps up
Michael> when I run firefox (1.5.x thru 3.0.5) and ramps up
Michael> exponentially faster for pages that have flash content.
Michael> Killing/quiting firefox frees up a lot of memory, but not
Michael> from Xorg's overall total. It has behaved like this (for
Michael> me) for the past couple of years. Only reason it's not a
Michael> big deal for me is I'm constantly having suspend/resume
Michael> issues since the 7.10 release, so uptime never exceeds a
Michael> couple of weeks anymore. :(
Hmm, thinking about this makes it pretty clear to me know. It really
must be firefox + flash. My firefox on x86 recently also acquired
about 1.5GB of RAM with the X server running at more than 2GB. Killing
the firefox instance also released quite a lot of RAM from the X
server. But more importantly: As reported earlier, I don't have the
problem on my amd64 desktop at work. And guess what! I don't have a
flash plugin running for my firefox there.
So please debugger folks. Test along these lines, and I am almost
certain you will find the real cause of this.
Roland