Re: OK, what can I do about Opera's never-ending thirst for memory?!
Eirik Byrkjeflot Anonsen <[email protected]>
| Newsgroups | gmane.comp.web.opera.linux |
|---|---|
| Message-ID | <[email protected]> |
Daniel Eckl <[email protected]> writes: > Hi Eirik! > > [...] >> Of course, this changes a lot of variables, so I'm not sure how much we >> can learn from it. > [...] >> Given that it seems to be a rather uncommon problem, I'm not sure that >> would tell us much, though. It's changing too many things at once :) > > As well for 64-bit to 32-bit change, as for trying on another PC, it > would give a hint if there is any cause in the local settings, in the > many image gallery pages Kenny uses or so on. If taking the whole > opera config and saved session to another machine and the problem is > gone, then we don't need to focus on the web pages itself, nor on > cache settings or cache locations and so on and so forth. It's all > about ruling out variables, you know? Then we could go back to the > main system and look at filesystem, file allocators etc.pp. Local settings, yes. One of the first things to try is probably to move the .opera directory out of the way and see if the problem is still reproducible. > > Don't be afraid of trying big changes first to get a rough direction > on where to look ;) Agreed :) (But it helps when the big changes have some sort of common "direction". Which admittedly can depend heavily on the observer...) 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