Summary: | [r300g] games crash with pp_jimenezmlaa=8 | ||
---|---|---|---|
Product: | Mesa | Reporter: | Pavel Ondračka <pavel.ondracka> |
Component: | Drivers/Gallium/r300 | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | cand, pedretti.fabio |
Version: | git | ||
Hardware: | Other | ||
OS: | All | ||
URL: | http://www.heroesofnewerth.com/download.php | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Pavel Ondračka
2011-09-11 02:23:29 UTC
Same problem here. Depending on the app the assertion changes, e.g. with torcs: ../../../../src/gallium/auxiliary/util/u_inlines.h:81:pipe_reference_described: Assertion `pipe_is_referenced(reference)' failed. with glxgears: util/u_sampler.c:69:default_template: Assertion `desc' failed. Surprisingly, pp_jimenezmlaa_color=8 and pp_celshade=1 works fine. See also my report here: http://phoronix.com/forums/showthread.php?59152-Gallium3D-Post-Processing-MLAA-Nearly-Ready&p=225721#post225721 Disabling pageflipping also seems to help here. And BTW I don't have any problems with glxgears. I tried postprocessing now, and here are my results on rv350 with current r300g; the test application is neverball. pp_nored=1 pp_nogreen=1 pp_noblue=1 are OK pp_celshade=1 I don't know what this should look like, but the colors are weird pp_jimenezmlaa=2 pp_jimenezmlaa=4 pp_jimenezmlaa=8 r300: Ooops. Got unsupported format none in r300_create_sampler_view. r300_state.c:1490:r300_create_sampler_view: Assertion `hwformat != ~0' failed. Trace/breakpoint trap pp_jimenezmlaa_color=2 pp_jimenezmlaa_color=4 Segmentation fault (renders only blackness, memory leaks very fast) Is this still an issue with the latest mesa git? (In reply to comment #4) > Is this still an issue with the latest mesa git? Yes Fixed in commit 7219af5ec184d4f92682e75f3d992ae048005d6a ('gallium/postprocess: Proper reference counting of pp_jimenezmlaa depth buffer.') |
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.