Findit results:
----------------
Suspected CLs	The result is a list of CLs that change the crashed files.

Author: mlippautz
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/871a920f3be1968d6c461aad7e893f3a82919b36
Time: Fri Oct 28 17:17:33 2016
Lines 1913, 2005 of file Node.cpp which potentially caused crash are changed in this cl (frame #0, "blink::Node::mutationObserverRegistry"; frame #1, "blink::Node::unregisterMutationObserver").
Minimum distance from crash line to modified line: 0. (file: Node.cpp, crashed on: 2005, modified: 2005).

Suspected Project: chromium
Suspected Component: Blink>DOM

based on Findit results, assigning to mlippautz@, could you please check the issue and update.

Cannot reproduce so far. Any detailed instructions on how to repro this one would be useful.

So far I did the following:
- Checkout web-platform-tests
- Checkout testharness.js
- Copy all relevant files (repro, webaudio/*, testharness*) to a local directory
- Start the python http server
- Run the downloaded build.

I see the test passing.

ClusterFuzz has detected this issue as fixed in range 432416:432464.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5645629587193856

Fuzzer: inferno_twister_custom_bundle
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x000000000010
Crash State:
  blink::Node::mutationObserverRegistry
  blink::Node::unregisterMutationObserver
  blink::MutationObserver::disconnect
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_lsan_chrome_mp&range=428348:428482
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_lsan_chrome_mp&range=432416:432464

Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv95GvWxF83ZMCLBI6k5jmO6mbveU6S9TmFF96GuhgvQ4Klxx_UKIY4826eK1K5t_tF2SRmyvGFVdof1MELLQoFGgWhKxEZPEDJqsHrZv621X_6dPieeU8t-v7blijSqYxqUg2sARAFNUEsyC_VqYHw5rjJ5AdXYEYkae1a9eHZ_ykRYecRM?testcase_id=5645629587193856


Additional requirements: Requires HTTP

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

CF says it's fixed.