Bug 74459 – [Chromium] Ensure that DumpRenderTree does not crash for tests that use MessagePort

• Component: WebCore Misc.
• Status: RESOLVED WONTFIX

[Dmitry Lomov]

These tests currently crash:

fast/workers/termination-with-port-messages.html = CRASH
fast/workers/worker-cloneport.html = CRASH
fast/workers/worker-context-multi-port.html = CRASH
fast/workers/worker-messageport-gc.html = CRASH
fast/workers/worker-messageport.html = CRASH
fast/workers/worker-multi-port.html = CRASH

[Dmitry Lomov]

Here is an offending stack trace:
The key problem is that MessageLoop::current() is null on worker thread chromium DRT

#5  0x0ba25300 in MessageLoop::AddToIncomingQueue (this=0x0, pending_task=0xb2b0fee8) at /Users/dslomov/work-mac/new-chromium/src/base/message_loop.cc:632
#6  0x0ba25069 in MessageLoop::PostTask (this=0x0, from_here=@0xb2b10060, task=0x6f4c960) at /Users/dslomov/work-mac/new-chromium/src/base/message_loop.cc:260
#7  0x0b799bae in TestWebMessagePortChannel::postMessage (this=0x6f21660, data=@0xb2b100f0, ports=0x0) at /Users/dslomov/work-mac/new-chromium/src/webkit/support/test_webmessageportchannel.cc:69
#8  0x0b533db3 in WebCore::PlatformMessagePortChannel::postMessageToRemote (this=0x6f21620, message=@0xb2b10128) at PlatformMessagePortChannel.cpp:193
#9  0x0b533b59 in WebCore::MessagePortChannel::postMessageToRemote (this=0x6f214d0, message=@0xb2b10180) at PlatformMessagePortChannel.cpp:80
#10 0x0cfd37ab in WebCore::MessagePort::postMessage (this=0x6f5abc0, message=@0xb2b101f8, ports=0xb2b10250, ec=@0xb2b101fc) at MessagePort.cpp:94
#11 0x0d70c6b3 in handlePostMessageCallback (args=@0xb2b10370, extendedTransfer=false) at V8MessagePortCustom.cpp:63
#12 0x0d70c46c in WebCore::V8MessagePort::postMessageCallback (args=@0xb2b10370) at V8MessagePortCustom.cpp:70
#13 0x0c191286 in HandleApiCallHelper (args={<v8::internal::Arguments> = {<v8::internal::Embedded> = {<No data fields>},

[Stephen Chenney]

Test related bugs being marked WontFix. TestExpectations will contain bug if still relevant.