1453194 - Assertion failure: aWidth > 0, at /builds/worker/workspace/build/src/gfx/2d/DataSurfaceHelpers.cpp:24

Status: RESOLVED WORKSFORME

(Core :: WebRTC, defect, P2)

Description

[Jason Kratzer [:jkratzer]]

Attachment: trigger.html

Testcase found while fuzzing mozilla-central rev a8061a09cd70.

rax = 0x0000000000000000   rdx = 0x0000000000000000
rcx = 0x00007f6d92dd82dd   rbx = 0x00007f6d764c7c80
rsi = 0x00007f6d930a7770   rdi = 0x00007f6d930a6540
rbp = 0x00007ffc60560680   rsp = 0x00007ffc60560680
r8 = 0x00007f6d930a7770    r9 = 0x00007f6d94171740
r10 = 0x0000000000000039   r11 = 0x0000000000000000
r12 = 0x00007ffc605607b0   r13 = 0x00007f6d69e04b50
r14 = 0x00007f6d69e04a90   r15 = 0x00007ffc605609b8
rip = 0x00007f6d81a56811
OS|Linux|0.0.0 Linux 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC 2018 x86_64
CPU|amd64|family 6 model 78 stepping 3|1
GPU|||
Crash|SIGSEGV|0x0|0
0|0|libxul.so|mozilla::gfx::StrideForFormatAndWidth|hg:hg.mozilla.org/mozilla-central:gfx/2d/DataSurfaceHelpers.cpp:a8061a09cd7064a8783ca9e67979d77fb52e001e|24|0x18
0|1|libxul.so|mozilla::MediaEngineTabVideoSource::Draw|hg:hg.mozilla.org/mozilla-central:dom/media/webrtc/MediaEngineTabVideoSource.cpp:a8061a09cd7064a8783ca9e67979d77fb52e001e|332|0xb
0|2|libxul.so|mozilla::MediaEngineTabVideoSource::StartRunnable::Run|hg:hg.mozilla.org/mozilla-central:dom/media/webrtc/MediaEngineTabVideoSource.cpp:a8061a09cd7064a8783ca9e67979d77fb52e001e|40|0x10
0|3|libxul.so|mozilla::MediaEngineTabVideoSource::InitRunnable::Run|hg:hg.mozilla.org/mozilla-central:dom/media/webrtc/MediaEngineTabVideoSource.cpp:a8061a09cd7064a8783ca9e67979d77fb52e001e|103|0x3
0|4|libxul.so|nsThread::ProcessNextEvent|hg:hg.mozilla.org/mozilla-central:xpcom/threads/nsThread.cpp:a8061a09cd7064a8783ca9e67979d77fb52e001e|1096|0x15
0|5|libxul.so|NS_ProcessNextEvent|hg:hg.mozilla.org/mozilla-central:xpcom/threads/nsThreadUtils.cpp:a8061a09cd7064a8783ca9e67979d77fb52e001e|519|0x11
0|6|libxul.so|mozilla::ipc::MessagePump::Run|hg:hg.mozilla.org/mozilla-central:ipc/glue/MessagePump.cpp:a8061a09cd7064a8783ca9e67979d77fb52e001e|97|0xa
0|7|libxul.so|MessageLoop::RunInternal|hg:hg.mozilla.org/mozilla-central:ipc/chromium/src/base/message_loop.cc:a8061a09cd7064a8783ca9e67979d77fb52e001e|326|0x17
0|8|libxul.so|MessageLoop::Run|hg:hg.mozilla.org/mozilla-central:ipc/chromium/src/base/message_loop.cc:a8061a09cd7064a8783ca9e67979d77fb52e001e|319|0x8
0|9|libxul.so|nsBaseAppShell::Run|hg:hg.mozilla.org/mozilla-central:widget/nsBaseAppShell.cpp:a8061a09cd7064a8783ca9e67979d77fb52e001e|157|0xd
0|10|libxul.so|XRE_RunAppShell|hg:hg.mozilla.org/mozilla-central:toolkit/xre/nsEmbedFunctions.cpp:a8061a09cd7064a8783ca9e67979d77fb52e001e|893|0x11
0|11|libxul.so|mozilla::ipc::MessagePumpForChildProcess::Run|hg:hg.mozilla.org/mozilla-central:ipc/glue/MessagePump.cpp:a8061a09cd7064a8783ca9e67979d77fb52e001e|269|0x5
0|12|libxul.so|MessageLoop::RunInternal|hg:hg.mozilla.org/mozilla-central:ipc/chromium/src/base/message_loop.cc:a8061a09cd7064a8783ca9e67979d77fb52e001e|326|0x17
0|13|libxul.so|MessageLoop::Run|hg:hg.mozilla.org/mozilla-central:ipc/chromium/src/base/message_loop.cc:a8061a09cd7064a8783ca9e67979d77fb52e001e|319|0x8
0|14|libxul.so|XRE_InitChildProcess|hg:hg.mozilla.org/mozilla-central:toolkit/xre/nsEmbedFunctions.cpp:a8061a09cd7064a8783ca9e67979d77fb52e001e|719|0x8
0|15|firefox|content_process_main|hg:hg.mozilla.org/mozilla-central:ipc/contentproc/plugin-container.cpp:a8061a09cd7064a8783ca9e67979d77fb52e001e|50|0x14
0|16|firefox|main|hg:hg.mozilla.org/mozilla-central:browser/app/nsBrowserApp.cpp:a8061a09cd7064a8783ca9e67979d77fb52e001e|280|0x11
0|17|libc-2.23.so||||0x20830
0|18|firefox|MOZ_ReportAssertionFailure|hg:hg.mozilla.org/mozilla-central:mfbt/Assertions.h:a8061a09cd7064a8783ca9e67979d77fb52e001e|164|0x5

Comment 1

[Tyson Smith [:tsmith]]

The attached test case no longer triggers the issue and it was last seen by fuzzers in February 2019. I assume this has been fixed elsewhere.