binaryninja-api: Consistent crashes/hangs when navigating binaries

Version and Platform (required):

• Binary Ninja Version: 3.1.3482-dev
• OS: Windows
• OS Version: 10.0.25131.1000
• CPU Architecture: x64

Bug Description: Binary Ninja tends to crash or hang when navigating around a binary. It takes 30-60 minutes for the problem to occur in a normal reversing session, but it can be triggered reliably within 10-20s by rapidly navigating over a wide area with the feature map.

The problem tends to manifest as a hang on smaller binaries and a crash on larger binaries, so there might be different issues at play here.

Steps To Reproduce: Grab any binary from the Binaries folder here: https://drive.google.com/drive/folders/1as90hOalwG8djJNNzbkFpKNT4t2eqFzk

Load up the binary and let analysis complete, then navigate randomly. A good way to trigger the crashes/hangs in a timely fashion is to rapidly flick the mouse around in the feature map for 10-20s, going back and forth between code and data sections.

Expected Behavior: No crashes.

Additional Information: If there’s a way to get Binary Ninja to print a stack trace when crashing, I can provide them.