This topic has been closed. No new entries allowed.
Reason: Duplicate thread, non-descriptive title.
You need to be logged in to post in the forums. If you do not have an account, please sign up first.
Frustration Unlimited: Why can't Opera fix cache?Opera is doing something in cache that has created a succession of bugs, where one fix just creates yet another bug, each worse than the one before.
Once upon a time, there was Opera 9.27, and there was peace in Operaland, more or less.
Then along came Opera 9.5, and hope shattered. Opera removed the extensions from cache files, and 9.27 became a fork in the Opera family with capabilities not seen since.
Meanwhile, Opera 9.5 had a nasty habit of steadily consuming cpu cycles when doing nothing, just displaying a blank tab. I turned off preferences, history, remember content in visited pages but that made no difference. Opera kept right on consuming cycles with a blank screen. I did not see any disk or network activity when Opera did this.
See <a href="http://my.opera.com/community/forums/topic.dml?id=242685&t=1216160675&page=1">Why Does Opera Consume CPU cycles doing nothing?</a>
This was an annoyance. If you were a desktop user, you would not have know of the problem unless you monitored your cpu utilization. If you were a laptop user, you had to close Opera for the power management to turn your system off. If you were paranoid, the lack of disk and network activity provided some level of comfort.
I just discovered, quite belatedly, that with 9.64 if you turned off disk cache completely, Opera cpu utilization would go to zero, as it should. The turn off cache problems really began with version 9.5, not 10.
Next Opera 10.0 came along. I discovered that with a blank screen Opera would go to zero cpu utilization. It fixed the mysterious background processing in 9.5. That was progress, so I thought.
However, I discovered an nastier bug in 10. For some reason, Opera 10 usually ended up with 100 percent cpu utilization when I used it. When I browsed mostly text only sites, this didn't seem to happen.
I discovered some posts saying turn off the disk cache. I did. I then no longer saw Opera hitting 100 percent, except when I had flash on. Unlike when Flash takes the cpu to 100%, when Opera hit 100% here, some interrupts got through. The Opera 100% was not as bad as the Flash 100%. I didn't discover it myself until it had happened a few times. This bug rose above the annoyance of the 9.5 background processing problem.
See <a href="http://my.opera.com/community/forums/topic.dml?id=291100&t=1252736007&page=1">Opera uses 10x processor power that it should</a>
Next Opera 10.10 beta build 1830 came along. It appears that Opera may have fixed the 100% bug. I say appears because I haven't encountered it so far. However, I never knew what caused it in the first place and I might not yet have run into it.
However, once again, it looks like Opera has replaced one bug with another one, and the new one is a doozy. Like clockwork every six to eight minutes, Opera locks up and doesn't take keyboard and mouse interrupts, for 15-20 seconds. After the lockup, it then processes all the queued keyboard and mouse entries. The cpu utilization during this period is around zero.
See <a href="http://my.opera.com/community/forums/topic.dml?id=292558&t=1253314007&page=1">Delayed Execution of Screen Down Commands - Beta testing (including snapshots and previews)</a>
This bug is the worst yet. You are reading an article and key page down to see the next screen. Nothing happens, and you realize nothing will happen for 15-20 seconds and there is nothing you can do about it. You have to sit there and wait for Opera to eventually give you the next screen. This one drives me insane, sitting there and waiting for Opera to wake up.
I have to wonder what is Opera doing with cache that has produced this chain of bugs? Why periodically turn off interrupts? Why couldn't they have left alone what once worked fine.
Will peace ever return to Operaland?