The crash seems to be in RingbufferDumper::DumpRingBuffer_s ... called from MOZ_ReportAssertionFailure This looks like broken debug output. High P2, it may be valuable to fix the debug output to not crash, so we can learn more about failures of this type, and not have them show up as crashes.
Priority: -- → P2
My guess is that RingbufferDumper::OnTestPartResult() http://searchfox.org/mozilla-central/rev/5dadcbe55b4ddd1e448c06c77390ff6483aa009b/media/mtransport/0 and RingbufferDumper::OnTestEnd() could race and the ring buffer could get destroyed before getting dumped. If that's whats going on here it only affects our gtest. We probably need ref-count when doing the WrapRunnable calls in RingbufferDumper.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.