The teardown solution used in #234 re-invokes volatile CPs. During un-rendering of an application, the invocations may attempt to calculate based on no-longer-valid state.
Furthermore afaik d3 instances should be exit() and remove(), and the handlers will be GC'd by Chrome. There is possibly something going on here and this is possibly a mitigation or fix, but neither of those PRs actually describe what is going on in more detail than "event handlers should be removed" (which is guidance that does not apply to Chrome).
This reverts:
The teardown solution used in #234 re-invokes volatile CPs. During un-rendering of an application, the invocations may attempt to calculate based on no-longer-valid state.
Furthermore afaik d3 instances should be
exit()
andremove()
, and the handlers will be GC'd by Chrome. There is possibly something going on here and this is possibly a mitigation or fix, but neither of those PRs actually describe what is going on in more detail than "event handlers should be removed" (which is guidance that does not apply to Chrome).