Cache issues since around Opera 10.50 Beta 2 for Windows?

Cache issues since around Opera 10.50 Beta 2 for Windows?

If anyone is experiencing problems with the cache since around beta 2 for Windows (build 3273), please let us know in this thread.

I think it's fixed in 10.52 build 3333

I can confirm the streaming videos issue is still there, both on 3333 and 3337, Win XP.

Originally posted by netwolf:

Did you try a (really) clean install?
Or delete old cookies4.dat file?

For me, at least cookies are no issue anymore so far with 3333.

I tried deleting the dat file. Still - without cookies enabled globally I can't even log in to my.opera and other sites.

Originally posted by Cyro:

Yeah, I want to know if caching is fixed, specially all this specific problem concerning flash videos. Please update status.

Some of the cache issues have been fixed and released in a snapshot. Other fixes are ready and they will be tested soon.
Flash issue: I'm not sure that it is related to the cache module, but of course it has to be fixed. It is under analysis.
Delete on exit: I will check it soon.

Thanks for the status update.

It looks like caching is back in the latest build. Can't really confirm as my connection got 3 times faster before Easter. Lucav, can you confirm and say what to look for?

Video download but is still active in build 3344

The main issue still there should be the video download, that is currently under investigation.
Also there is a corruption still present in the public releases, but it seems that you are not really affected by it (or you did not realize that it was a cache problem...).
The corruption involves having multiple tabs using the same site, a cache full, some time, and also some "luck". But a fix will be tested very soon.

And also the problem about Delete on Exit should be fixed now. :-)

Thanks, lucav. Please, do not forget about "Check documents" timings, as now all of them except "Never" are redirected to "Always". I mean, page's html is reloaded, every time, even if it is set to check "Once a week". Opera 10.10 respected them. Thanks again!

When using Galaxyzoo, Opera insists on downloading everything every time a new galaxy is to be classified, which is frustrating and pointless.

Now, I love Opera for all kinds of reasons and truly appreciate the integrated nature of it but a development team should be established to ensure that basic core functionality is not sacrificed in the pursuit of developing the new, exciting features like Link, Unite, Wand etc etc.

Basically, keep an eye on the core functionality because there is now lots of competition for the ABIE population.

Originally posted by jkforde:

but a development team should be established to ensure that basic core functionality is not sacrificed in the pursuit of developing the new, exciting features like Link, Unite, Wand etc etc.

Basically, keep an eye on the core functionality because there is now lots of competition for the ABIE population.

We try to do that. The problem is that testing a browser is a lot more complicated than what it seems, and Opera 10.50 was also rushed for the ballot screen.

Anyway, do the latest snapshot improve the situation of the cache?

There still seems to be one issue with the cache: when a file is referenced with multiple slashes (e.g. http://example.org/styles//moo.css ) it is always taken from cache whereas calling http://example.org/styles/moo.css would rerequest the file correctly.

Sometimes some pages don't load completely (transmission stops).
Anyone else experienced this?

Originally posted by lucav:

Anyway, do the latest snapshot improve the situation of the cache?

No striking improvements. I thought it works better but it was only a placebo from cleared cache loaded with some fresh data. After two days - browsing feels the same to the point that I stopped testing cache. This build was the last one. I'll resume cache testing when it will give performance improvements similar to Opera 10.10 or every other browser.

• [3347] memory and disk cache set to 400 MB.
• Check documents always and check images never.
• Cache was cleared after installation.
• http://www.megatokyo.com/scr33n/scr33n_2010-04-13_51221.png 1.5 MB in size.
• Close Opera and reopen Opera without closing the tab the image is cached there.
• Close the tab and then close Opera and then reopen Opera and reopen image and image is not cachced.

My network speed got about 5-10 times faster now. Is there a way to limit network speed on Windows x64? Or is there any way to monitor which elements are taken from cache in Opera plus some basic time measurements?

Pheewwww...finally confirmed to be fixed in build 3363. Happy days

That's good. Waiting for "Cache re-enabled"

I always "start" with a fresh cache after installation of a new snapshot by deleting the cache folders and loading a session with tens of tabs of the most frequent sites I visit. The few recent builds used to generate less than 20 MB of content in cache folder. The latest one - over 100 MB. Something has moved. We'll see.

What bug fix was this? I don't see it listed in the changelog: http://my.opera.com/desktopteam/blog/2010/04/16/fixing-bugs but the cache problem does appear to be fixed with this build.

Ooops...forgot to mention. I was talking about the video bug.

Fixed DSK-288607 (Flash video continues to download after tab is closed)

Cache fixed is a bold statement IMO. There will still be issues with basic caching functionality, I guess. After all there has to be a reason not to mention cache fixes in the changelog at all. Examples:

• 
  flash content being cached but is not loaded from cache (IMO it either should be loaded from cache or there should be an option to disable caching of large files)

• Opera Turbo compressed images are not cached. I can't confirm it though. If it is like that it's simply ridiculous

For now I enjoy 10.10-like browsing. I can report that manually removing large files from cache seems to have no negative effect on cache functionality which is a consolation to the issue I mentioned earlier.

I can agree with that statement Bucic. I'll say that cache works better with the build [3363]. For example, I do not like how images will partially load, then stop drawing for unknown reasons until the image is fully loaded.

If they load like that then it's not a cache specific issue, isn't it?

For me all the big issues gone, but I'm sure that you will proof me wrong...
Some of the issues that you perceive as "cache problems", are in reality present in other components (for example Flash loading on a closed tab), so I'm not sure about their status.

I will soon submit the latest changes, but Opera 10.52 should already have the most interesting fixes.

Please point out when I blame cache module by mistake and you may be sure that I won't do it again Point out when I provide a useless report and I'll think twice before sending a similar one next time. My aim is to help you get the caching fixed, not to satisfy my God knows what issue by pointing out Opera bugs I just need perfect caching for my stone-aged connection.

For now the only issue I can report is that Opera still caches streaming media (YT for sure) but does not load it from cache on the next visit. I already tried my luck with Media Cache Size but it failed. I was hoping to limit the individual cached file size to 1 MB. It was a lucky shot as many of new config entries remain undocumented. It is desirable Opera has such a config entry in the future.

I'm currently using 10.52 final.

Another issue. Contents are not being loaded from cache when I enable proxy. Tested here for example - http://forums.eagle.ru/member.php?u=5409

The proxy is w3cache.pw.edu.pl:8080, http 1.1. enabled

Hi, I think this might be the best thread to comment an Opera behaviour I've been noticing in the last weeks (months maybe), because it smells of "faulty cache behaviour"...

It feels like a kind of a bug, but I'm not sure. It has to do with "History Navigation mode = 3" in opera:config (which means, INSTANT back and forward navigation). I always use opera with this setting set to "3" (I've been doing it for years, and I change it from 1 to 3 whenever I do a clean installation, not very frequently thankfully)...

The thing is that when Opera has been running for, I don't know, 3-4 hours (it's inconsistently reproducible), even with this setting still set at "3", Opera reloads webpages when doing the back and forward navigation actions (keeping forms info, in case there was any).
People could say this missbehaviour is not really slow (for me it is), but compared with proper "history navigation mode = 3" it's unbearably slow.
My memory cache setting is set to "auto" (or else, history navigation mode=3 wouldn't work, as far as I remember). And I haven't messed with these settings for ages...

Anyone else noticing these "history navigation mode =3 " inconsistencies? It's not worth a bug report because it happens randomly... Something unknown triggers it...

I'm currently using build 3390 XP SP3, but I've been noticing this missbehaviour for weeks, probably months...

Greetings!

Hi... Anyone? (echo... echo...)
I can't believe no one notices this severe bug...

Much needed bump!

I have seen that behaviour incidentally. I also use Fast History Navigation (History Naviagation Mode = 3) with RAM on automatic. Disk cache set to 200 MB. May be (RAM) cache is full and overflowing? Just thinking out loud. I am on Win 7 x86.

I'm a HNM=3 user as well, and typically keep Opera open all day (close it at night, of course, since Opera is rapacious about memory), but I can't say that I've seen this behavior. There are a few pages where HNM always tends not to work (not that I can think of any right now), but I don't see an abrupt shift where it stops working on all pages. I'll definitely watch for it though.

What I AM seeing, under this umbrella cache topic, is Opera several times an hour doing something strange with VPS (I know this by using Process Monitor and watching for it). I don't know if it's writing that out more frequently in 10.54 (I think this only started happening with the 10.54 builds, but it's possible that it started with 10.53), but whatever is happening, it causes Opera to spike the CPU and "pause" for several seconds while it's dealing with VPS. It's extremely annoying since you lose control of the browser for this time. I'm using the same "7500 Addresses" that I always have. Are there any other controls for this, any way to curb what it's doing?

10.54 Build 3394

Does not update the web pages with the latest information.

I have under:> check if cached page is updated on the server
Check documents:> Always
Check images:> Always

memory cache is set to auto
disk cache is set to 200mb
empty on exit is not checked.

I have to always check by bringing up Firefox 3.7a5pre (minefield) to see if anything is updated on my web pages that I go to such as Tomshardware which is updated frequently. Opera I have to hit F-5.

Why is the cache not looking at the server and seeing the new updated website?

Bump...

"History navigation mode=3" (cache related, as far as I understand) ceases to work after some time using opera. Even with build 3400 10.60 (XP SP3).
Known fact?

Lightning fast instant navigation (back and forward) doesn't show! ALL pages become reloaded... What might be the reason behind this (not only faulty, but annoying) behaviour Opera has been showing for many builds?

Right now, browsing 'process explorer' "working set" column, I can see Opera is using 584 MB (I have 1500 MB Physical installed memory), and steadily growing... (From time to time, it decreases usage, but it acts rising slowly slowly slowly, and then drops 1 MB).

Besides, "Virtual size" column shows 1537 MB, FAR BEYOND any other alive process on my system now... It grows slowly also... (now, it's 1538 MB).

Greetings...

Cannot confirm the History Navigation = 3 bug mentioned above ^ (and I mostly have Opera open for a day or so).

I am having this issue again, since the latest build 3400, or maybe even the previous one, 3394 (no idea if it regressed and is it known or whatever is going on):

Originally posted by sutekh:

When I have one my.opera.com page open, and then I open another one (another my.opera page) and it starts loading, the sprite images in the main top bar in the first loaded tab (messages icon, my avatar, background of the bar, and the backgrounds of home, community, forums and opera buttons) get redownloaded every single time and disappear from the first tab until they load in that second tab.

Anyone else seeing something like this?

Can confirm "fast history navigation" becoming slow quite fast.

HNM=3 has now stopped working for me entirely as of the last two builds. It's a setting somewhere apparently running interference, since a separate install with a clean profile doesn't show the problem. Yet.

HNM set for fast (3) is broken. Last tested with build 3428.

It seems, after two of the (FREQUENT) 10.60 builds (one fixed the images part and another one the documents part), History Navigation Mode = 3 bug is finally fixed !! Today's build (3442 for windows), did finally the trick. YAY!!!

10.60 will be sharp, quick and sleek again, BRAVO OPERA TEAM GUYS!!

Yes, though I sure wish someone would parse the following statement so that it's comprehensible:

CORE-30940 (Fast history navigation stops working when document cache reaches half the size of where it used to stop working)

Bump, HNM=3 is broken again... (Build 3451 XP SP3)

Any update on HNM=3 from the powers that be? Rather than our guessing and redundantly reporting, it would be helpful if we knew. Something during the course of normal usage cause HNM=3 to stop working until the browser is restarted. This happens in all 10.70 builds.

HNM=3 is supposed to stop working when Documents memory usage is around 80% when you checkopera:memdebug. If you see that it stops working for you before that limit is hit then I guess it could be a bug.

If on the other hand it works according to what I wrote then if you really want to make HNM=3 work longer you have to raise the limit.

To do it:
* note max value for Documents, Images, EcmaScript on opera:memdebug page before changing anything
* disable opera:config#UserPrefs|AutomaticRAMCache
* set opera:config#Cache|Document to something bigger than your previous value - 500000 for example
* set opera:config#Cache|Figure and opera:config#Cache|ECMAScript to noted values (you might want to increase Ecmascript cache if you hit its limit too).

Thanks d.i.z., I'll watch it, but I'd never heard of opera:memdebug before or the threshold you mention or the ways to possibly work around it. When did all this come about? It wasn't that long ago that it just used to work indefinitely. Something with 10.5?

I think it was always like that (ignoring some builds in between that had bugs that lowered the limit even more).

10.10 had no Carakan so it was using less memory so you might have not even hit it there.

BTW. This thread was more about disk cache and not memory cache so the thing we are discussing is not really relevant to this thread.

Well deserved bump... Does history navigation mode work as of today? What's its exact purpose nowadays?

I haven't noticed any change from what d.i.z. mentions above. You need to have HNM=3 on and to manually set your Document figure to have any kind of consistency with it.