Bug 96841

Summary:	Recover from eglSwapBuffers() errors in gl_renderer_repaint_output()
Product:	Wayland	Reporter:	Miguel A. Vico <mvicomoya>
Component:	weston	Assignee:	Miguel A. Vico <mvicomoya>
Status:	RESOLVED MOVED	QA Contact:
Severity:	enhancement
Priority:	medium	CC:	michel, mvicomoya, wayland-bugs
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:
Attachments:	attachment-2984-0.html

Description Miguel A. Vico 2016-07-07 10:15:14 UTC

Currently, if eglSwapBuffers() fails in gl_renderer_repaint_output(), only an error message is logged.

Compositors should be allowed to recover from such errors, or abort if the error is fatal.

This bug is intended to track the progress of adding some mechanism to notify compositors of an eglSwapBuffers() call, and let them take the appropriate action.

Adding a callback in libweston might be a good solution to explore.

Comment 1 Daniel Stone 2018-06-04 08:09:12 UTC

The backend repaint has the same issue: if, e.g., an atomic commit fails, then we just go into stasis for that output until you do something drastic like VT switching.

Comment 2 Daniel Stone 2018-06-04 08:10:12 UTC

*** Bug 99546 has been marked as a duplicate of this bug. ***

Comment 3 GitLab Migration User 2018-06-08 23:54:42 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/wayland/weston/issues/79.

Comment 4 Miguel A. Vico 2018-06-08 23:54:50 UTC

Created attachment 140101 [details]
attachment-2984-0.html

Dear sender,


I'm out of the office starting on 06/08 until 06/12 (inclusive) with limited email access. Expect some delay in my responses.


For urgent, non-confidential matters, you can try to reach me at my personal email address: mvicomoya@gmail.com.


Thanks,
Miguel.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.