Nonetheless, my computer's total "Commit" soars to more than 2GB,
which is twice my real memory (RAM), while using 9.27/Win32,
and Windows has just informed me
that even my paging file isn't large enough,
not to mention that everything "freezes" for long periods.
Without Opera in the picture, 600MB total "Commit" is rarely exceeded.
Can this be stopped? (clearing cache seems to have no influence whatsoever)
Thanks for your interest.
--
9.27 is *very* old, you should really update to 10.10, although I guess
you have your reasons for sticking with 9.27.
Something that is very likely the cause: flash or java. Since they are run
in process it goes into Opera memory usage while it's really something
else using it. It's been quite a while since I've touched 9.27, and I
can't even run it now since there is no 64-bit linux version. I'd say
you're pretty much on your own here.
--
Remco Lanting
[Unofficial Opera bug tracker links]
http://opera.remcol.ath.cx/bugs |
http://my.opera.com/community/forums/topic.dml?id=217364 |
remco.lanting...@gmail.com
On Nov 24, 12:15 pm, "Remco Lanting"
> How many tabs do you have running ?
Around 32, with flash/javascript enabled in 10.10 on linux. It's been
running since Saturday, November 21 and at the moment is using a bit less
than 600MB of RAM (with plenty free)
--
Remco Lanting
[Unofficial Opera bug tracker links]
http://opera.remcol.ath.cx/bugs |
http://my.opera.com/community/forums/topic.dml?id=217364 |
> Can this be stopped? (clearing cache seems to have no influence
> whatsoever)
Do you subscribe to newsfeeds? There was a memory leak in some versions of
Opera 9. This was fixed in Opera 10.
--
\\// Peter Krefting - Core Technology Developer, Opera Software ASA
> How many tabs do you have running ?
Suppose there are ten;
would this mean that the browser
normally uses 200MB of RAM per open tab?
I guess that would mean that this version of Opera
can not run at all on a 128MB computer, even on Win98 :)
--
> Do you subscribe to newsfeeds?
> There was a memory leak in some versions of Opera 9.
> This was fixed in Opera 10.
I subscribe to a couple of feeds,
which receive a few new items per week.
Would that lead to leaking something more than 1GB
in perhaps a few hours?
It's a wonder I haven't bled to death all this while :)
--
> 9.27 is *very* old, you should really update to 10.10,
> although I guess you have your reasons for sticking with 9.27
Many, which quite a few readers can guess,
even if they hadn't read my original postings on these matters ;-)
> Something that is very likely the cause: flash or java.
> Since they are run in process it goes into Opera memory usage
> while it's really something else using it.
No Java, but some flash (e.g. tabs viewing YouTube);
most of these are actually not using the flash,
since I keep "plug-ins" disabled most of the time,
but enable now and then to actually view a few.
If flash can eat up so much memory (2-4GB on my 1GB computer),
uncontrollable by browsers and unaffected by purging cache,
and since quite a few sites won't even load without flash,
then it must take a 3-4GB computer at minimum
(which may be more than some versions of Windows can even use :)
to survive internet surfing these days!
I'm actually not being "drowned" in page thrashing right now
(0.9 GB "Commit," down from an earlier peak of 4.0),
so it's not an "all time" thing, but sometimes it grows faster
than ever did the financial industry's losses on derivatives ;)
Thanks again for your input.
--
> I subscribe to a couple of feeds, which receive a few new items per week.
>
> Would that lead to leaking something more than 1GB in perhaps a few
> hours?
I don't recall exactly how much was leaked, but if you have them all set
to update every five minutes (which you can), then it would leak faster
than if you set them to update every week.
JHM:
>> I subscribe to a couple of feeds, which receive a few new items per week.
>> Would that lead to leaking something more than 1GB in perhaps a few hours?
PK:
> I don't recall exactly how much was leaked,
> but if you have them all set to update every five minutes (which you can),
> then it would leak faster than if you set them to update every week.
I have never found where any such setting exists,
so it seems likely that my setting may be a default.
"History" > "Check documents" (and images) are both "every 5 hours,"
if that's in any way related.
If that's it, then I've had a 1GB leak in less than five hours,
so I guess it must leak 1GB on every feed check -- I wonder
why that wasn't more noticeable than seems to have been reported?
--
> On Thu, 26 Nov 2009 02:23:10 -0600, Peter Krefting wrote:
>
> JHM:
>>> I subscribe to a couple of feeds, which receive a few new items per
>>> week.
>>> Would that lead to leaking something more than 1GB in perhaps a few
>>> hours?
>
> PK:
>> I don't recall exactly how much was leaked,
>> but if you have them all set to update every five minutes (which you
>> can),
>> then it would leak faster than if you set them to update every week.
>
> I have never found where any such setting exists,
> so it seems likely that my setting may be a default.
>
> "History" > "Check documents" (and images) are both "every 5 hours,"
> if that's in any way related.
>
In the feeds panel, right-click on a feed and select Properties. There,
you'll fund the setting you're looking for.
[snip]
--
Ken Knox
Opera 10.00.1750
> In the feeds panel, right-click on a feed and select Properties.
> There, you'll fund the setting you're looking for [how often to check]
Thanks. Each of my four feeds says "every 3 hours" (probably the default).
My 1GB "memory leak" within a few hours still seems pretty large,
particularly if attributed to a these few RSS feed checks :)
--
As far as I can fathom,
if terminating Opera returns all the memory,
and total system memory usage (according to Process Explorer)
then goes back down from about twice the real memory (RAM)
to about half the real memory, then there was no "memory leak,"
and Opera was simply running up memory usage without limit,
despite having been told a limit of at most 60MB for memory cache.
So telling Opera to limit its memory usage
is about as effective as telling a teen-ager to limit anything :)
--