I didn't know whether to post this under Issues or under FamilySearch, but it seems to me to be more of an RM issue than a FamilySearch issue, so I am posting here.
I have had several instances lately where RM7 locks up when I click on the FamilySearch icon to go look at a matched person in FamilySearch. The process of getting into FamilySearch is successful. I look at the person in FamilySearch, make no changes, and close the browser window. RM is now locked up. RM is not in a loop because it is taking no CPU cycles. But it is completely unresponsive. The only way out is to use Task Manager to kill RM and then to restart RM.
It's hard to know how to get any diagnostic information to help identify the cause of the problem. And I don't expect or want any effort to go into solving this in RM7. I do hope that RM8 locks up less and has fewer invalid address kinds of errors than RM7. We shall see. With its less modal design, RM8 is going to have to be very careful about such issues. I'm pretty convinced that a lot of RM7's problems in this area have to do with background tasks that are performed in threads that are not being properly synchronized. That's why I think RM8 will have to be especially careful about proper synchronization between its non-modal windows.