Re: Huge memory-footprint problem SOLVED! It's GNOME's fault!
Eirik Byrkjeflot Anonsen <[email protected]>
| Newsgroups | gmane.comp.web.opera.linux |
|---|---|
| Message-ID | <[email protected]> |
Kenneth Crudup <[email protected]> writes: >> Hmmm ... there's some 19,000 files in that directory; if GNOME's file- >> selector is leaking every time I save a file (sometimes as many as 300 >> per day), that's something to consider. > >> I've changed opera:config to use the Qt selector instead. Let's see >> how this does. (I didn't save many files on the session running XVnc). > > Since doing this, I haven't seen Opera run more than about 2.8GB working, > and it subsequently dropped back to its quiescent value of ~1.6GB. > > So Opera Devs (et al.)- the problem lay with *GNOME*! (Is it too late to > go "Ah, I knew Opera wasn't at fault!" :) That is certainly a strong hint. Bug report? (Or add a comment to the already existing bug report, if there is such a thing...) It may have something to do with running the gtk/gnome file chooser on top of qt. But this is completely unknown code to me, so I don't know. [...] > Also, I figured out what the deal is with the million file-descriptors- > NEVER use "Automatic" memory cache- if I set it there for some reason it > creates a huge amount of *on-disk* cache files that don't go away; I think > that might actually be a bug (right now I'm using a 400MB disk cache > size for testing, and with maybe some 80 tabs open I've only got 13 > cache files open and 82 open FDs). Make a bug report. This feels like it could be a possible explanation. (Although it is probably not because it is "automatic", but because it is big. If I understand correctly, "automatic" is a fraction of available memory, which is unreasonably much on modern computers.) eirik -- Opera-Linux: https://list.opera.com/mailman/listinfo/opera-linux More lists: https://list.opera.com/mailman/listinfo/ Unsubscribe: mailto:[email protected]?subject=unsubscribe