search

pacificIT / chromiumembedded

Automatically exported from code.google.com/p/chromiumembedded
0 stars 1 forks source link

CSS animations gobble CPU and memory #558

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Open the attached test page in cefclient.exe
2. Check CPU and memory usage in Windows Task Manager

CEF version 1.1046.516
OS: Windows XP / Windows 7

Any CSS animation chews the equivalent of 1 core on our quad core machines.  
Also, memory usage rises over time.

And here's the weird part: If you shrink the size of the cefclient window to 
about 400x400, CPU usage drops to zero.

I've tried all the possible values for CefSettings.graphics_implementation

I've tried setting CefBrowserSettings.accelerated_compositing_enabled to true.

I've also tried setting all the CefBrowserSettings.accelerated_*_disabled flags 
to true;

Nothing seems to make any difference.

BTW, I believe this is the root cause of issue 194.

Original issue reported on code.google.com by powerbf...@gmail.com on 28 Mar 2012 at 5:16

Attachments:

GoogleCodeExporter commented 9 years ago 
Forgot to mention that running the same animation in Chrome uses about 10% of 
one core (i.e. about one tenth the CPU usage of cefclient.exe).

The Chrome version I'm using is "18.0.1025.140 beta-m".

Original comment by powerbf...@gmail.com on 28 Mar 2012 at 6:04

GoogleCodeExporter commented 9 years ago 
Just tested with CEF 1.1046.537 (which has a differnt version of Chrome to CEF 
1.1046.516).

Unfortunately, the issue still exists.

Original comment by powerbf...@gmail.com on 29 Mar 2012 at 8:39

GoogleCodeExporter commented 9 years ago 
Err...that should be "different version of Chromium"

Original comment by powerbf...@gmail.com on 29 Mar 2012 at 8:40

GoogleCodeExporter commented 9 years ago 
For me, versions 1.963.439 and 1.1025.607 use 1% CPU with your example and 
cefclient.exe in release build.

Are you using a debug or release build executable? CPU usage with a debug build 
is significantly higher. Version 3.1082.566, for example, uses 6% CPU in the 
debug build and 2% CPU in the release build.

Original comment by magreenb...@gmail.com on 22 May 2012 at 4:49

GoogleCodeExporter commented 9 years ago 
This bug doesn't contain any actionable items.

Original comment by magreenb...@gmail.com on 3 Oct 2012 at 5:47