On 11/05/2020 06:11, Carlos E. R. wrote:
But the first hour it stays under 1 Gig, and it responds fast and snappy. Then over the days it grows and grows bigger and slower.
That's also a characteristic of a memory leak. It maybe a simple memory leak, for example in a plug-in/add-on. Or it might be a systemic memory leak, for example in the handling of attachments and embedded imaged. The observations James makes about Firefox, also Mozilla code, make me wonder about that. Then again, if that's so, why isn't everyone suffering from this? These are also gnome-context (or GTK rather than QT context) items. Maybe its configuration there that is the problems. So many possible interactions. My point here is that this isn't happening to me; I zypper up regularly and run a KDE/plasma environment. I have 8G on a an old machine - 'lscpu' tells me Model name: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz One note: I run FF with one process, two windows. I tried moving some tabs off to a third window as an effort at 'grouping'. It absolutely killed performance, not just for FF but the whole machine. Not swapping, something else. Load factor went up from the normal <2.5 to >25 I have one xterm running 'vmstat' so I can both swap, disk IO and memory as well as CPU, and also how much of disk IO is devoted to swap. it also shows interrupts and context switches. That latter is what was alarming. I suggest that 'vmstat -SM -a 15' in an xterm will tell you more about what's going on than 'top'. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org