System.InvalidOperationException: Collection was modified; enumeration operation may not execute. about snoopwpf

[cplotts]

@perlun this seems to be an issue in the application that you were Snooping (and not with Snoop itself).

Since Snoop actually injects itself into the Snooped process, exceptions that happen there might seem to come from Snoop ... when they do not.

Unless you can provide some sample code that illustrates otherwise ... I am going to close this issue.

[perlun]

@cplotts Thanks. No longer working actively on that project, so we can safely close this for now unless we find a way to reproduce it.

Can application-generated exceptions be re-thrown from the Snoop.Shell.VisualTreeProvider.OnSyncSelectedItem method?

[batzen]

To be honest, i think this is a bug in snoop itself.

We are using linq here which evaluates lazy and we are using a timer to refresh things.
If the evaluation/refresh take longer than the timer interval, which currently is 250ms, we modify the list we are currently working on.
The problem is that there is no guard against re-entrancy etc..

While debugging i noticed that the powershell integration adds quite some overhead, like this timer and everything it does on tick, even if you don't use the powershell tab at all.

[cplotts]

I'll reopen this ... I honestly didn't look close enough. @batzen I think you are right.

I wonder if we could limit the impact of the PowerShell tab by only starting this timer when the tab is active.