1453718 - blob-invalidation: Crash in [...] | webrender::renderer::Renderer::update_texture_cache

Status: RESOLVED FIXED

(Core :: Graphics: WebRender, defect, P1)

Description

[Darkspirit]

Nightly 61 x64 20180412100111 de_DE 246c614e160586c1eb3167cff866dd550be35e03 @ Debian Testing, KDE, Radeon RX480
fresh profile: gfx.webrender.all, gfx.webrender.blob.invalidation

Suspicion: Bug 1453090 might have morphed the crash from bug 1452409 into this one. I don't know how to enable the regular crash reporter inside mozregression and -B debug doesn't enlighten me either.

STR from bug 1452409 comment 2:
> gfx.webrender.all + gfx.webrender.blob.invalidation.
> Just open https://web.basemark.com, click on Start and wait about a minute. Got a browser crash at "SVG Test (10/20)".

bp-b5b0b744-6a83-462d-988e-dacc70180412 12.04.18 17:49 (browser crash)
> slice index starts at 88297052 but ends at 1048576

bp-b49449f3-8a7f-496d-bf89-c828b0180412 12.04.18 18:40
> slice index starts at 88297052 but ends at 1048576

I couldn't reproduce without blob-invalidation.

Comment 1

[Jeff Muizelaar [:jrmuizel]]

Looking at this now...

Comment 2

[Jeff Muizelaar [:jrmuizel]]

I can reproduce it in rr

Comment 3

[Jeff Muizelaar [:jrmuizel]]

Actually, I mistook, that's the PopClip crash that I reproduce. Let's see...

Comment 4

[Jeff Muizelaar [:jrmuizel]]

I have it now.

Comment 5

[Jeff Muizelaar [:jrmuizel]]

This actually might be fixed by bug 1452401

Comment 6

[Jeff Muizelaar [:jrmuizel]]

Looks like it isn't.

Comment 7

[Jeff Muizelaar [:jrmuizel]]

It looks like the problem is an interaction with large tiled blob images and dirty rects

Comment 8

[Jeff Muizelaar [:jrmuizel]]

This should be fixed by https://github.com/servo/webrender/pull/2653