Originally Posted by melstrom
12 Oct 2007
Culver City, CA
Opera 9.23 running under Slackware 12 (dropline GNOME) on a 1.7GHz Dell Latitude D800 (500 MB ram; 40 GB hard drive). Absolute dog. Thrashing my hard disk.
Got a similar problem on an old Ubuntu box. The 'thrashing the disk' is the problem and 'poor opera performance' is the symptom (even if it is caused by, amongst others, Opera's memory usage).
I usually have as many as a dozen tabs open.
I used to work with up to 50 (at which point, the tab icons get kind of small). No more. Can't go beyond a dozen now.
It happens for me whichever browser I use. It hapens a bit more quickly with Opera than with Firefox or Konq, presumably because I tend to use more open tabs with Opera than with the others. It started for me just after a system update and my suspicion is that I've got an underlying library that has a memory leak, but that was also roughly the time that I started using RSS feeds more heavily.
I've used akregator for RSS feeds now and I don't run unnecessary programs, but that only helps a little. I still have to log out and log in every three or four days or less (previously, I'd log out and in every month or three - that is completely impossible now). These days, I can't live without RSS feeds and, like you, I prefer Opera.
The suggestion has been made to me that there is a memory leak in X, but as the person who made that suggestion was using a different distro and a different X, I'm not sure. My feeling is that an underlying library is actually leaking and that, maybe, it has something to do with two cpus andwhether all the libraries are 'threadsafe'.
If I run 'ksysguard' with a really slow update interval (~100 seconds), I can actually see the memory usage slowly growing over 6-8 hours. Once I've got to 500+M swap out of 1G total, logging out and in is becoming inevitable.
So far, I haven't taken this very seriously as this box is due an update. I just haven't decided on Debian(Etch)/Kubuntu 7.10/SuSE 10.3 yet. Maybe, I have to try them all. Of course, that assumes the update makes it go away...