Closed Bug 1470440 Opened 5 years ago Closed 5 years ago

thread '<unnamed>' panicked at 'assertion failed: `(left == right)` left: `2048×8192`, right: `2048×162568`', gfx/webrender/src/


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




Tracking Status
firefox-esr60 --- unaffected
firefox62 --- disabled
firefox63 --- disabled
firefox64 --- fixed


(Reporter: truber, Assigned: emilio)


(Blocks 3 open bugs)


(Keywords: assertion, testcase)

Crash Data


(1 file)

Attached file testcase.html
The attached testcase causes an assertion in m-c 20180622-6b6f3f6ecf14 with pref("gfx.webrender.all", true)

thread '<unnamed>' panicked at 'assertion failed: `(left == right)`   left: `2048×8192`,  right: `2048×162568`', gfx/webrender/src/
#0: mozalloc_abort
        at memory/mozalloc/mozalloc_abort.cpp:34
#1: abort
        at memory/mozalloc/mozalloc_abort.cpp:81
#2: panic_abort::__rust_start_panic
        at src/libpanic_abort/
#3: std::panicking::rust_panic
        at src/libstd/
#4: std::panicking::rust_panic_with_hook
        at src/libstd/
#5: std::panicking::begin_panic
        at src/libstd/
#6: std::panicking::begin_panic_fmt
        at src/libstd/
#7: webrender::renderer::Renderer::draw_tile_frame
        at gfx/webrender/src/
#8: webrender::profiler::TimeProfileCounter::profile
        at gfx/webrender/src/
#9: webrender::renderer::Renderer::render_impl
        at gfx/webrender/src/
#10: webrender::renderer::Renderer::update
        at gfx/webrender/src/
#11: mozilla::wr::RendererOGL::UpdateAndRender(bool)
        at gfx/webrender_bindings/RendererOGL.cpp:132
#12: mozilla::wr::RenderThread::UpdateAndRender(mozilla::wr::WrWindowId, bool)
        at gfx/webrender_bindings/RenderThread.cpp:308
#13: mozilla::wr::RenderThread::NewFrameReady(mozilla::wr::WrWindowId)
        at gfx/webrender_bindings/RenderThread.cpp:223
#14: mozilla::detail::RunnableMethodImpl<mozilla::wr::RenderThread*, void (mozilla::wr::RenderThread::*)(mozilla::wr::WrWindowId), true, (mozilla::RunnableKind)0, mozilla::wr::WrWindowId>::Run()
        at xpcom/threads/nsThreadUtils.h:1165
#15: MessageLoop::RunTask(already_AddRefed<nsIRunnable>)
        at ipc/chromium/src/base/
#16: MessageLoop::DeferOrRunPendingTask(MessageLoop::PendingTask&&)
        at ipc/chromium/src/base/
#17: MessageLoop::DoWork()
        at ipc/chromium/src/base/
#18: base::MessagePumpDefault::Run(base::MessagePump::Delegate*)
        at ipc/chromium/src/base/
#19: MessageLoop::RunInternal()
        at ipc/chromium/src/base/
#20: MessageLoop::Run()
        at ipc/chromium/src/base/
#21: base::Thread::ThreadMain()
        at ipc/chromium/src/base/
#22: ThreadFunc
        at ipc/chromium/src/base/
Flags: in-testsuite?
This testcase is nearly identical to the one in bug 1470439.

bp-b5ecc69a-fc90-41bf-a663-29c400180622 (same crash signature as bug 1441392)
Crash Signature: [@ webrender::renderer::Renderer::draw_tile_frame ]
It looks like this bug has been fixed. I can't reproduce the issue any more
I'm apparently getting this from scrolling down the server list on discord ( At least according to what the crash reports are getting assigned with:
We can't release this to the field, but we can let this ride to beta.
Priority: P1 → P2
Blocks: wr-fuzz
This currently ranks #1 in the list of crashes with webrender in the signature:

Interestingly, all of the reports I have seen so far have 

> |[0][GFX1-]: Attempting to allocate a texture of size 4294967293x2048 above the limit, trimming (t=102.156) 

in the gfxCriticalError log. 4294967293x2048 looks suspicious (FFFFFFFD).
Was fixed by Will land a crashtest.
Assignee: nobody → emilio
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
Flags: in-testsuite? → in-testsuite+
You need to log in before you can comment on or make changes to this bug.