It’s unfortunate, but bugs do happen, and this has the smell of one.
If your project is not confidential, you can upload it here to see if anyone of us can reproduce it before making a bug report. (But you need to gain some “experience” first to get though the anti-spam bot. See: New Member Information)
If your project is confidential, you can create an issue on gitlab and mark your issue as confidential. That way only a small group of people can see it. But they can not help you without the project itself.
If you can narrow down the issue to a small part of your project (maybe a schematic symbol or footprint), then you can also do the above with just that part of the project that shows this behavior. Making a list of the parts that need the “rescue” would be a first attempt in narrowing the issue down. The developers are also a scarce resource for KiCad. Bugs that crash KiCad get a very high priority, but anything you can do to make your project smaller and thus easier for them to analyze is a plus.