Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upgpu_cache hits debug_assert over mismatched epochs #2667
Closed
Comments
|
I'll look at this today. |
|
@kvark is already looking into this :) |
|
it's possible this was caused by #2588 |
|
Yup, that seems quite likely to be the cause of it. |
bors-servo
added a commit
that referenced
this issue
Apr 18, 2018
GPU cache invalidation fix and extra checks Fixes #2667 This PR is a bag of small things: - 420dd5b adds debug-only checks to make sure all the batches being rendered have been prepared correctly. It didn't fire for my limited testing, but I find it useful anyway for the peace of mind. - 78ca661 brings more symmetry to the prepare/add duopoly, checking for the filter to be visible on the other side - f280d47 fixes the GPU cache invalidation. If the epoch has already been updated, means the cache entry belongs to a different primitive, and we have no rights to access it. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/webrender/2671) <!-- Reviewable:end -->
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Scrolling around https://gankro.github.io/blah/webtests/text.html in gecko causes this very quickly (may need to shrink window vertically)
It seems to be related to text-shadows, as in release builds they will fail to render when first scrolled onto screen (and this is very visible thanks to APZ).
The assertion is in
GpuCache::get_address, but my stack seems to be messed up:Bugzilled: https://bugzilla.mozilla.org/show_bug.cgi?id=1454538