(In reply to comment #3)
> AFAICT this only happens if postprocessing is enabled via one of the pp_*
> driconf options or environment variables.
> 
> (In reply to comment #0)
> >     Bisecting revealed the culprit commit to be
> > "58d2afa2232060b88f9c444ce7a0d6e63c841bb2: radeonsi: fix leaking the bound
> > state on destruction v2".
> 
> Christian, any ideas?

That looks like a bug in the post processing cleanup to me. The context the
shaders belong to is destroyed before pp_free is called to destroy the shaders
created from that context.

Since the bisected patch explicitly destroys all bound shaders of a context if
the context is destroyed we get a double free of the shader.