Summary: | Rendering issues in SolveSpace | ||
---|---|---|---|
Product: | Mesa | Reporter: | Nazar Mokrynskyi <nazar> |
Component: | Drivers/DRI/i965 | Assignee: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Status: | RESOLVED FIXED | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Severity: | normal | ||
Priority: | medium | CC: | michel, mkyral |
Version: | 18.2 | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Nazar Mokrynskyi
2018-09-29 12:29:38 UTC
Maintainer of SolveSpace here. I've been seeing numerous mystifying issues with i965 graphics with SolveSpace, including rendering issues and massive video memory leaks (dozens of MB per frame), all of which are not present with LIBGL_ALWAYS_SOFTWARE=true; there are no GL errors and no GL object leaks as far as I can tell by calling glGetError() appropriately and analyzing traces with apitrace. I would be very happy if anyone gave me any pointers at all for resolving these issues. Hello, Nazar and Peter. Could you, please make a trace of issue with utility apitrace and upload it here? Sorry, no need in trace at this moment. Bisected: commit aefac10fecc9ec70feb5923ce3200902f67182ba Author: Michel Dänzer <michel.daenzer@amd.com> Date: Tue Sep 4 12:18:19 2018 +0200 loader/dri3: Only wait for back buffer fences in dri3_get_buffer We don't need to wait before drawing to the fake front buffer, as front buffer rendering by definition is allowed to produce artifacts. Fixes hangs in some cases when re-using the fake front buffer, due to it still being busy (i.e. in use for presentation). Cc: mesa-stable@lists.freedesktop.org Bugzilla: https://bugs.freedesktop.org/106404 Bugzilla: https://bugs.freedesktop.org/107757 Tested-by: Olivier Fourdan <ofourdan@redhat.com> Reviewed-by: Thomas Hellstrom <thellstrom@vmware.com> Potential fix: https://patchwork.freedesktop.org/patch/254198/ Fix sent out for review: https://patchwork.freedesktop.org/patch/254393/ Sergii, is there an easy way to exercise this code path with a piglit test? (In reply to Michel Dänzer from comment #5) > Fix sent out for review: https://patchwork.freedesktop.org/patch/254393/ Hi, I just tested this patch with mesa-18.1.9 on Gentoo Linux with i965 and SolveSpace now works correctly. Thanks Hello, Mark. | Sergii, is there an easy way to exercise this code path with a piglit test? Yes, will try to look but after 'dying light'.... Thanks for the report, fixed in Git master: Commit: c20ba1be1843d035f36e9794bee7aea9abfc2f8b URL: http://cgit.freedesktop.org/mesa/mesa/commit/?id=c20ba1be1843d035f36e9794bee7aea9abfc2f8b Author: Michel Dänzer <michel.daenzer@amd.com> Date: Mon Oct 1 18:43:46 2018 +0200 loader/dri3: Also wait for front buffer fence if we triggered it |
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.