GNOME Bugzilla – Bug 792742
White screen on 32-bit systems on some pages
Last modified: 2018-01-23 20:51:34 UTC
Could you check on 32 bit systems if e.g., http://www.youtube.com/watch?v=2TEH7DTaHvo https://www.youtube.com/playlist?list=PL38C412C876528CCB https://github.com/fyookball/electrum/pull/397 result in a final white empty screen after fully loading? They work fine on 64-bit systems. Also they are fine in Webkit Minibrowser.
Nope, I don't have access to a 32-bit system. But just from seeing the list of pages you posted, I'm quite confident that accelerated compositing mode must be broken on 32-bit. Can you move this to WebKit Bugzilla, please? Thanks for taking the time to report this. This issue is most likely a bug in WebKit. Please report the bug to https://bugs.webkit.org/ including a link to this bug report and noting the version of WebKitGTK+ that you have installed. When reporting the WebKit bug, be sure to include the prefix '[GTK]' in the bug summary and select the 'WebKit Gtk' component.
But they are fine in Webkit Minibrowser.
OK, that is interesting! Perhaps I guessed wrong. I suppose something could be wrong in the Epiphany web extension... if you try building Epiphany, do you see any warnings *from the compiler*? Anything related to wrong integer or pointer size would be suspect. Unfortunately, this will be hard to debug unless there is a build warning pointing us directly to the problem: someone with 32-bit hardware will have to step through the code until the problem is discovered. Still, just in case it is somehow related to AC mode, please do check and see if the usual workaround for broken accelerated compositing fixes those pages: $ WEBKIT_DISABLE_COMPOSITING_MODE=1 epiphany -p Also worth opening up the settings pane in MiniBrowser and confirm that the hardware acceleration policy is set to "ondemand". Try changing it to "always" and see if that allows you to reproduce the issue there.
Created attachment 367332 [details] Nobody can inspect or change the values of items in MiniBrowse, only see their names
OK upgrade libwebkit2gtk-4.0-37:i386 2.19.3-1 2.19.6-1 seems to have fixed it.
As for minibrowser, I submitted https://bugs.webkit.org/show_bug.cgi?id=182005 .