Bug 167492 - [GTK] Stop forcing accelerated compositing by default
Summary: [GTK] Stop forcing accelerated compositing by default
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: WebKit Local Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: Gtk
Depends on:
Blocks:
 
Reported: 2017-01-27 00:39 PST by Carlos Garcia Campos
Modified: 2017-01-27 07:10 PST (History)
2 users (show)

See Also:

Attachments
Patch (2.61 KB, patch)
2017-01-27 00:49 PST, Carlos Garcia Campos 		zan: review+
Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Carlos Garcia Campos 2017-01-27 00:39:53 PST 
We are now ready to bring back the on demand accelerated compositing mode with the threaded compositor. Unfortunately, having AC always enabled brought  a lot of issues for many people. Not only it requires a lot more memory but also caused rendering issues (or even nothing rendered at all) with some graphics drivers. People started to use WEBKIT_DISABLE_COMPOSITING_MODE as a workaround, but that was not expected to be used by users. So, entering/leaving AC when required by web contents is not actually the solution but a huge improvement for many people. If we are eventually ready to force AC mode again, we'll change this again. Note that we still have WEBKIT_DISABLE_COMPOSITING_MODE, but now also WEBKIT_FORCE_COMPOSITING_MODE for testing and debugging.
Comment 1 Carlos Garcia Campos 2017-01-27 00:49:34 PST 
Created attachment 299917 [details]
Patch
Comment 2 Carlos Garcia Campos 2017-01-27 00:55:51 PST 
Committed r211277: <http://trac.webkit.org/changeset/211277>
Comment 3 Sergio Villar Senin 2017-01-27 07:10:14 PST 
\o/