Intermittent crash in /html/semantics/tabular-data/processing-model-1/span-limits.html

[jdm]

This demonstrates a limitation of ipc-channel on mac, since the error is "Send is too large for port" in this case:

  ▶ CRASH [expected OK] /html/semantics/tabular-data/processing-model-1/span-limits.html
  │ 
  │ VMware, Inc.
  │ softpipe
  │ 3.3 (Core Profile) Mesa 17.3.0-devel
  │ called `Result::unwrap()` on an `Err` value: Custom { kind: InvalidData, error: StringError("Send is too large for port") } (thread LayoutThread PipelineId { namespace_id: PipelineNamespaceId(0), index: PipelineIndex(NonZero(NonZero(1))) }, at libcore/result.rs:916)
  │ 2018-02-16 19:40:56.616 servo[84415:1565670002] Metadata.framework [Error]: couldn't get the client port
  │ stack backtrace:
  │    0:        0x102c76ade - backtrace::backtrace::trace::h1572cbde15e97645
  │    1:        0x102c772cc - backtrace::capture::Backtrace::new::h0ca27cd1e659fd9b
  │    2:        0x100760299 - servo::main::_$u7b$$u7b$closure$u7d$$u7d$::h150b5a1bc30cce2d
  │    3:        0x102c7c610 - std::panicking::rust_panic_with_hook::h47a0773bed022912
  │    4:        0x102c7c42e - std::panicking::begin_panic::h357aa9770ebb9277 (.llvm.7D0B5603)
  │    5:        0x102c7c383 - std::panicking::begin_panic_fmt::h8146069d366cb090
  │    6:        0x102c7c2f2 - rust_begin_unwind
  │    7:        0x102cb2573 - core::panicking::panic_fmt::hde64b9c715e999e9
  │    8:        0x10250d9dd - core::result::unwrap_failed::h6615b7cb2ca1e628
  │    9:        0x102512a5e - webrender_api::api::RenderApi::send_transaction::hedfe6788f6c28aa8
  │   10:        0x1009b6e83 - profile_traits::time::profile::h70001ea9131fc72d
  │   11:        0x100a136b1 - layout_thread::LayoutThread::perform_post_style_recalc_layout_passes::hd269430e5d2cdb7d
  │   12:        0x100a118f9 - layout_thread::LayoutThread::handle_reflow::hacc4dec6eddfbe30
  │   13:        0x1009b624f - profile_traits::time::profile::h516947d164223246
  │   14:        0x100a0b7be - layout_thread::LayoutThread::handle_request_helper::h372a2e214e81fcd2
  │   15:        0x100a0a2b5 - layout_thread::LayoutThread::start::h863b03da023cad1f
  │   16:        0x1009768d8 - profile_traits::mem::ProfilerChan::run_with_memory_reporting::h100c25283ac94227
  │   17:        0x100a21f4a - std::sys_common::backtrace::__rust_begin_short_backtrace::h49c9cb5ca070bf1d
  │   18:        0x1009dda1d - std::panicking::try::do_call::h610ac6d5dfb67d10 (.llvm.9DF80B70)
  │   19:        0x102ca6e4e - __rust_maybe_catch_panic
  │   20:        0x100a666e3 - _$LT$F$u20$as$u20$alloc..boxed..FnBox$LT$A$GT$$GT$::call_box::haf3edc5f6f18bef7
  │   21:        0x102c8fc07 - std::sys_common::thread::start_thread::h1ef8cf6b973abe77
  │   22:        0x102c92f88 - std::sys::unix::thread::Thread::new::thread_start::h88d15e6243c319fe
  │   23:     0x7fff8f1d499c - _pthread_body
  │   24:     0x7fff8f1d4919 - _pthread_start
  │ ERROR:servo: called `Result::unwrap()` on an `Err` value: Custom { kind: InvalidData, error: StringError("Send is too large for port") }
  └ Pipeline failed in hard-fail mode.  Crashing!

[jdm]

This should be fixed by servo/ipc-channel#199.