[Webkit-unassigned] [Bug 101508] [EFL][WK2] Add API to limit number of compositing layers for mobile devices.

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=101508





--- Comment #4 from Viatcheslav Ostapenko <ostap73 at gmail.com>  2012-11-08 08:52:34 PST ---
(In reply to comment #3)
> (From update of attachment 172872 [details])
> Just counting layers is not the right way to limit resource use. You need to consider their backing store size. 

Actually, just big number of small layers also could be a problem for a slow CPU/GPU device, but I agree that several relatively large layers is bigger problem.
I was going to do memory limit as a separate patch, but may be there is better approach to do this instead of 2 different limits?

>Also when you hit this limit you'r breaking page rendering, because your z-ordering will be incorrect, 

I don't get it. Can it render correctly on single layer like in case when compositing is switched off? So far pages I've tried display normally, just work slower if they have some animations.

> and you'll fail to make compositing layers for things like video and 3d that require it.

IMHO, if device cannot handle all layers on the page should we really care about fancy things like video and 3d? The target is just to be able to show page readable in somewhat degraded mode. A lot of things work much slower in this mode because require layer image/texture updates. Of course if video and even 3d work that would be great, but I don't think it can be done correctly in all cases. For example, if video has some overlay on top and page switches do degraded mode, than we do layer for video and overlay will stay behind the video.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.