Deadlock in event handling when using Chrome about vugu

[bradleypeabody]

Interesting, and thanks for taking the time to write this up. Just a quick observation from fiddling with this for a bit: If I remove event.EventSummary() then I cannot reproduce the issue. I'm not entirely sure why though, since the event summary is already converted into primitive types and it's entire purpose is to provide context of the event without having to call back into the JS environment.

To your point, it definitely seems like something in there is calling back into the JS environment during the event handling, which is then firing another event, which then deadlocks.

Possibly that whole thing just need to be made more robust by having be tolerant to that scenario, although again I think it's key to track down how that is occurring here, since it is not obvious.