https://bugs.freedesktop.org/show_bug.cgi?id=106881
--- Comment #5 from Tapani Pälli <[email protected]> ---
(In reply to xinghua from comment #4)
> (In reply to Tapani Pälli from comment #3)
> > IMO this looks like a shader cache issue that got fixed by following commit.
> > Please pull the latest Mesa and test again.
> >
> > --- 8< ---
> > commit e266b320590ebbeadf7c98b0b493d89886534ccb
> > Author: Jordan Justen <[email protected]>
> > Date: Wed Jun 6 01:57:15 2018 -0700
> >
> > mesa/program_binary: add implicit UseProgram after successful
> > ProgramBinary
> >
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=106810
> > Fixes: b4c37ce2140 "i965: Add ARB_get_program_binary support using
> > nir_serialization"
> > Ref: 3fe8d04a6d6 "mesa: don't always set _NEW_PROGRAM when linking"
> > Ref: c505d6d8522 "mesa: use gl_program for CurrentProgram rather than
> > gl_shader_program"
> > Signed-off-by: Jordan Justen <[email protected]>
> > Reviewed-by: Plamena Manolova <[email protected]>
> > Reviewed-by: Timothy Arceri <[email protected]>
>
> Hi, Tapani, Thank you for your reply. I had tested this case again, the
> patch could resolve this issue.
> Could you give our more information about the root-cause in mesa, thank you.
Chrome browser implements a shader program cache using ARB_get_program_binary,
we had a bug in program binary code. Loading new binary was not binding the
shaders of the binary in to use (so old ones were still used). This is now
fixed.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
_______________________________________________
mesa-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
