The My Opera forums have been replaced with forums.opera.com. Please head over there to discuss Opera's products and features

See the new Forums

Google-related relative high CPU usage of Opera

Forums » Opera for Windows/Mac/Linux » Opera for *nix - Linux/FreeBSD

You need to be logged in to post in the forums. If you do not have an account, please sign up first.

Go to last post

3. December 2011, 03:50:34

xgdgsc

Posts: 11

Google-related relative high CPU usage of Opera

Recently I've found my opera takes approximately 20% of my cpu at any time,even long after I've minimized it and not used it .Then I found this:when I close all the google.com pages of opera,the CPU usage suddenly drops from 20% to a normal level of 1-2% and eventually 0%.I'm wondering if anyone else has this problem with their opera.Seems only happens when I open any webpage of Google.I'm using 64bit archlinux and I tried both opera 11.52 and 12(opera-next),same behavior here.Although 20% isn't unbearable,but google is what we use everyday and cannot afford to reopen every time.Hope developers would look into this issue.

3. December 2011, 16:04:01

Schnellinger

Posts: 78

I see this too, but I don't see why Opera devs should look at this issue. This mess comes from JS-heavy-overloaded crappy google search site, which once was usable, but now is really bloated.
I really don't need previews of search results and other gimmicks there. Either disable JS on google (which causes problems on other google related sites) or use a greasemonkey script that disables the useless code. I'm doing great with the later solution. But the reason why google is slow is not Opera, it is a company that makes his own browser and isn't interested in good performance on a concurrent product.

4. December 2011, 02:56:11

xgdgsc

Posts: 11

Turning off Javascript really works. However, since firefox turns out fine, why google just target at Opera---such a browser that takes so small percent of the market? Therefore, I still think opera devs should look at this issue and figure out what is really taking the CPU resources.

5. December 2011, 22:07:27

Schnellinger

Posts: 78

I don't think that they specially target Opera, but as as monopolist they try to dictate the things that a browser should do. "Best viewed in Chrome", deal with it or die, other browser developers. Like you said, we use it everyday. But you're right, maybe the Opera devs could help a bit. But Opera always have heavy load problems on sites with extensive JS. In such cases I tend to blame the web developers who don't keep their sites small am simple and try to trick them out with a user.js.

That was the greasemonkey script I spoke about http://userscripts.org/scripts/show/114455. Helped me with the heavy load problem, as it disables the 'Instant Preview' thing on google search

22. December 2011, 22:39:16 (edited)

MrbLOB9000

Posts: 17

I'm seeing the same thing, except it's not just google, random other pages exhibit the behavior too. It only started happening recently I think after getting 11.60. Before that Opera worked just fine.

Seems to be an Opera bug, not a Google conspiracy.

edit: (though I'm running it in Win7)

19. July 2012, 10:03:42

ameuret

Posts: 6

Originally posted by xgdgsc:

Turning off Javascript really works. However, since firefox turns out fine, why google just target at Opera---such a browser that takes so small percent of the market? Therefore, I still think opera devs should look at this issue and figure out what is really taking the CPU resources.



Still true today on Version 12.00 Build 1467 Platform Linux System i686, 3.2.0-26-generic-pae - Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz.

An empty, logged out, http://google.com home page burns 10% CPU continuously.

Only on Opera.

Sad state really.

--A

26. July 2012, 08:25:33

teresaejunior

Posts: 44

Me-tooing. Some javascript from Google Search is really wasting CPU cycles. Now I leave javascript disabled for google.com all the time, but it breaks many websites from Google. Very annoying.

29. July 2012, 03:03:53

teresaejunior

Posts: 44

I got to solve this problem by removing the "if(hostname.indexOf('.google.')>-1)" part from $HOME/.opera/browser.js. In my current setup it is deleting from line 771 to 796.

Yes, the bug is from Opera, not Google. I have filed a bug previously on this matter, but I don't know actually how to update the status of a Opera bug report...

Forums » Opera for Windows/Mac/Linux » Opera for *nix - Linux/FreeBSD