I have run into an interesting issue. It was happening at 12.3 and I have upgraded to 13.1 (64 bit both cases). Current FF is 29.0.1.
H/W: Dual core AMD 2.2GHz processor, 8GB RAM, RAID mirrored disks.
I run with multiple FF windows and tabs.
I have found that if I do not touch a tab after start of FF (where it reloads where it was as of last time it was running) that my CPU utilization by top or KDE sysguard monitor display, stays between 10-15% for both cores. I am seeing very little swap activity, and I never max out memory (I even have a VMware instance that runs W7, and it doesn't affect the system like FF w/ Flash).
However, if I use Pandora, and then pause it, the CPU load jumps to about 80% total. If I have other Flash sessions of any kind, the CPU usage will never drop below 40% unless I actually kill those tabs.
And I've noticed that this affects the ability to load patches and the like with Yast.
Anyone else seeing this?
Anyone got any ideas how to change tuning to fix it?
I have, once or twice, set FF down in dispatch priority, but the IP stack is still affected.
H/W: Dual core AMD 2.2GHz processor, 8GB RAM, RAID mirrored disks.
I run with multiple FF windows and tabs.
I have found that if I do not touch a tab after start of FF (where it reloads where it was as of last time it was running) that my CPU utilization by top or KDE sysguard monitor display, stays between 10-15% for both cores. I am seeing very little swap activity, and I never max out memory (I even have a VMware instance that runs W7, and it doesn't affect the system like FF w/ Flash).
However, if I use Pandora, and then pause it, the CPU load jumps to about 80% total. If I have other Flash sessions of any kind, the CPU usage will never drop below 40% unless I actually kill those tabs.
And I've noticed that this affects the ability to load patches and the like with Yast.
Anyone else seeing this?
Anyone got any ideas how to change tuning to fix it?
I have, once or twice, set FF down in dispatch priority, but the IP stack is still affected.