| Summary: | [GTK] White pages in AC mode: Cannot get default EGL display: EGL_BAD_PARAMETER | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Michael Catanzaro <mcatanzaro> | ||||
| Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | aperez, bugs-noreply, cgarcia, clopez, cmarcelo, ews-watchlist, gyuyoung.kim, Hironori.Fujii, luiz, mcatanzaro, noam, ryuan.choi, sergio, zeno | ||||
| Priority: | P2 | ||||||
| Version: | WebKit Nightly Build | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| See Also: |
https://bugs.webkit.org/show_bug.cgi?id=201507 https://bugs.webkit.org/show_bug.cgi?id=192558 |
||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 192523 | ||||||
| Attachments: |
|
||||||
|
Description
Michael Catanzaro
2019-09-30 06:07:36 PDT
Never happened here. Is this reproducible only with flatpak+epiphany_tech_preview? or is also reproducible outside of flatpak? What does about:gpu says? I wonder if it may be caused by incorrect graphic drivers inside the flatpak environment. So far I've only noticed it in Tech Preview, but that's because it's what I use as my daily browser. It's not reproducible at all, so it's not easy to check if it occurs outside flatpak without disruption. I'd have to use system Epiphany for several days to be confident the issue does not occur there. about:gpu is a blank page. Epiphany does not have an about:gpu and I don't think it ever did. (In reply to Michael Catanzaro from comment #3) > So far I've only noticed it in Tech Preview, but that's because it's what I > use as my daily browser. > > It's not reproducible at all, so it's not easy to check if it occurs outside > flatpak without disruption. I'd have to use system Epiphany for several days > to be confident the issue does not occur there. In which page have you noticed the problem? Even if it's very intermittent, if there is there some particular known to result in a white page when switching to AC mode would be already be of help. Here I tend to use Epiphany from distribution packages or built by me against system libraries, so I can try to help out and see whether it shows outside of Flatpak. > about:gpu is a blank page. Epiphany does not have an about:gpu and I don't > think it ever did. The support for about:gpu has landed just today (see bug #202305 for that), so I suppose it will take still a bit to be in Tech Preview :) (In reply to Adrian Perez from comment #4) > In which page have you noticed the problem? Even if it's very > intermittent, if there is there some particular known to result > in a white page when switching to AC mode would be already be > of help. Here I tend to use Epiphany from distribution packages > or built by me against system libraries, so I can try to help > out and see whether it shows outside of Flatpak. No, it's not any particular page. It's a UI process issue. When the issue occurs, all pages that trigger AC mode are white until the browser is restarted. Sorry if that wasn't clear enough from my initial report. > > about:gpu is a blank page. Epiphany does not have an about:gpu and I don't > > think it ever did. > > The support for about:gpu has landed just today (see bug #202305 for > that), so I suppose it will take still a bit to be in Tech Preview :) I'll try to get 2.27.1 into the runtime as soon as it's released, as usual (unless the MSE rework is not fixed first, in which case I'll skip releases until that's sorted). X11 or Wayland? wpe renderer or wayland compositor? Does resizing the browser window instead of restart fix it too? (In reply to Carlos Garcia Campos from comment #6) > X11 or Wayland? Wayland > wpe renderer or wayland compositor? WPE renderer > Does resizing the > browser window instead of restart fix it too? I'll try to find out. Well it's been two days and I haven't noticed this bug again, so maybe it's not as common as I'd feared. I've toggled AC mode back on in Epiphany... we can see how many bug reports we get between now and 3.36. OK, I'm seeing the bug right now and resizing the page does NOT help avoid the issue. I have warnings in my journal: Oct 04 08:14:31 chargestone-cave org.gnome.Epiphany.Devel.desktop[1896]: Cannot get default EGL display: EGL_BAD_PARAMETER Oct 04 08:14:31 chargestone-cave org.gnome.Epiphany.Devel.desktop[1896]: Cannot create EGL context: invalid display (last error: EGL_SUCCESS) Oct 04 08:14:32 chargestone-cave org.gnome.Epiphany.Devel.desktop[1896]: Cannot get default EGL display: EGL_BAD_PARAMETER Oct 04 08:14:32 chargestone-cave org.gnome.Epiphany.Devel.desktop[1896]: PlatformDisplayLibWPE: could not create the EGL display: EGL_SUCCESS. Oct 04 08:14:37 chargestone-cave org.gnome.Epiphany.Devel.desktop[1896]: Cannot get default EGL display: EGL_BAD_PARAMETER Oct 04 08:14:37 chargestone-cave org.gnome.Epiphany.Devel.desktop[1896]: Cannot create EGL context: invalid display (last error: EGL_SUCCESS) Oct 04 08:14:43 chargestone-cave org.gnome.Epiphany.Devel.desktop[1896]: Cannot get default EGL display: EGL_BAD_PARAMETER Oct 04 08:14:43 chargestone-cave org.gnome.Epiphany.Devel.desktop[1896]: PlatformDisplayLibWPE: could not create the EGL display: EGL_SUCCESS. If anyone is online *right now* and wants me to check something (e.g. attach with 'gdb -p') I can do so now. As soon as Epiphany or gnome-shell crashes we'll be out of luck until next time I see the bug. This seems to be related to bug #201507. Other bugs where we print EGL_SUCCESS as if it were an error: bug #178896, bug #178937, bug #195742 Created attachment 380417 [details] Patch This patch handles the EGL display initialization failure and disables AC, but it doesn't fix the actual bug. Let's figure out what's failing in bug #201507, since it's the same problem in the end. Comment on attachment 380417 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=380417&action=review > Source/WebCore/ChangeLog:9 > + reason. We need to understand why, but we should also handle the case of failing to initialize the WGL display WGL -> EGL? (In reply to Michael Catanzaro from comment #13) > Comment on attachment 380417 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=380417&action=review > > > Source/WebCore/ChangeLog:9 > > + reason. We need to understand why, but we should also handle the case of failing to initialize the WGL display > > WGL -> EGL? Yes, it's a typo. Committed r251122: <https://trac.webkit.org/changeset/251122> |