Inspecting variables and fields during breakpoint completely locks up Unity editor and has to be force restarted

I've had this issue for several months, but I couldn't figure out a way to reproduce it consistently. However I think I finally found an IDE functionality which seems to trigger this very reliably.

The user must place a breakpoint and hit this breakpoint from the Unity editor, whether it be game or editor code. This must be a script where you can navigate a lot of content in the 'Variables' panel of the debugger, navigating into a large object with many many fields and properties works well for this. Finally, begin typing to search for content.

It seems like searching is the consistent cause of this, because I've started using the search less to test it and have experienced very little freezing recently while debugging. Then, I just had a very short debugging session now where freezing occured once again after navigating through a large nested object's variables using the search.

If the freeze has occured, the user cannot switch back to Unity even after resuming execution. If you press the 'Stop' button to disconnect the debugger, it changes to a skull head and stays that way. Clicking the skull head force closes the debugger process, but Unity still does not come back to life. At this point, you can only force end the Unity process and start anew.