Comment 3 for bug 2012966

There's a decent chance this might be the same issue as #2012965 . That crash is hard to track down since it happen some time after the action that actually caused it, once the dotnet garbage collector runs