UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36

Steps to reproduce the problem:
When debugging memory leaks it would be nice to ignore some edges. Often the graph has a lot of edges that you know aren't an issue but make it difficult to find the issue.

For example, if the shortest path goes through a weak edge that is retained because of the other side ephemeron.

Cycles are another thing that add noise.  Basically the shortest path isn't always the most interesting it depends on the use case so there needs to be a way of saying I know this edge is ok.

Right now, we add a bunch of unnecessary teardown to reduce this noise in order to debug.

What is the expected behavior?

What went wrong?
Too much noise in retainers view.

Did this work before? N/A 

Chrome version: 65.0.3325.181  Channel: stable
OS Version: OS X 10.12.6
Flash Version: