| Summary: | Rendering artifacts created by long switch statement | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | Clive McCarthy <CliveMcCarthy> |
| Component: | Drivers/DRI/i965 | Assignee: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
| Status: | RESOLVED MOVED | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | git | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | a complete program that illustrates the issues | ||
|
Description
Clive McCarthy
2019-04-14 20:30:54 UTC
Whoops, looks like 18.2 does it too. Is this just the driver grabbing a chunk of working memory? In a small 4GB system it looks like a lot. I see no leak in my code but the system memory continues to be chewed up such that swap space is used. Created attachment 143980 [details]
a complete program that illustrates the issues
The attached code and libraries illustrate two issues:
[1] The strange behavior of the memory used -- the program itself has no leak
[2] Nasty artifacts that appear as an image is rendered.
Neither of these issues exist on a similar Linux system with an Nvidia GPU and driver.
I have boiled my code down to a minimum build-able set including my GLSL loader.
Thank you for working so hard on this issue. The FBO blitting turns out to be a red herring. My fragment shader is 'odd' in that is has large switch statement. This has caused the linking time to be rather long as reported in bug #91857 and, to my surprise, it also causes the artifacts I reported here and in bug #93676 I created a sample application that illustrates the problem. I'm afraid it will be troublesome to build but it is possible to reproduce the artifacts in it. The fragment shader's case statement has a #if ... #endif section that will enable/disable the artifact problem. *** Bug 93676 has been marked as a duplicate of this bug. *** -- 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/mesa/mesa/issues/1806. |
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.