[Opera-Linux] OK, what can I do about Opera's never-ending thirst for memory?!

[Kenneth Crudup]

On Tue, 16 Jun 2009, Daniel Eckl wrote:

> In March you already complained about that, but after my very serious
> try to help you, you did not even reply to my mail at all.
> http://list.opera.com/pipermail/opera-linux/2009-March/009894.html
> That's why I doubt you _really want_ any help.

Whoa- I missed that completely, I think!

Sorry you thought I was ignoring you. As far as determining the cause,
for the most part my system is fairly standard, an Ubuntu 9.04 system
that's really only got their updates on it. I'm running the NVidia
closed-binary driver, but I have my doubts as to that causing such
large increases in virtual/resident memory usage (it's so far and away
bigger than any other of the ~20-odd windows/programs I'd have up and
running at the time.

I've been running Opera for a few years now (since 2002, anyway) and
this is the only platform I've seen it on, but it's also the only one
that's:

 - a 64-bit platform
 - using the NVidia closed-source drivers
 - using Compiz

Again, I'd love to have something to send the devs (map usage, the output
of "inspectr" (is that finally running on the Linux/64 platform) but I
think in my mind it's just not releasing all the pixmaps (which could be
related to the display driver), but that's just my wild guess.

I guess I could suffer thru the "nv" driver for a while :) and see what's
up, but I develop on this system, too, and stuff like that might interfere
with work.

I have a AMD 64-bit system that's "headless" (i.e., I run the standard
Ubuntu GNOME desktop on it, but only thru XVnc server), I could maybe
move over one of the saved session files and run thru that, I guess.

	-Kenny

-- 
Kenneth R. Crudup  Sr. SW Engineer, Scott County Consulting, Los Angeles
O: 3630 S. Sepulveda Blvd. #138, L.A., CA 90034-6809      (888) 454-8181