Since we may update context state as we compute the batch, that state is preserved as we rollback the batch for a failed aperture check -- the subsequent emission then skips the atoms as the context state is believed to match requirements.
The aperture rollback has been in place since
Author: Eric Anholt <email@example.com>
Date: Sat Oct 22 09:37:57 2011 -0700
i965: Use the batch save/reset code to avoid needing the BO validate step.
The issue with believing global state for urb in particular seems to be from
Author: Jason Ekstrand <firstname.lastname@example.org>
Date: Fri Aug 18 16:10:39 2017 -0700
i965: Stop looking at NewDriverState when emitting 3DSTATE_URB
I'm not sure if that's the only instance.
-- 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/1728.