SDK Hangs/Lags on specific Blender Models

Hey Guys,
Hey @jmekaelthas

I know this is actually a SDK Problem and nothing with the Blender Importer but maybe Kaelthas can Imagine what's going on better than us.

I have a model file which works fine and really fast on the 3.0 SDK but when Importing on 3.1 (alpha5), I had to kill the SDK because after 7 minutes of loading it stopped logging triangulation errors and instead did nothing but that at 100% CPU Load 😄

I then tried to write a simple application, which also took long (3-4 minutes), spammed the log but finally managed to convert the file:

Spatial s = assetManager.loadModel("Blender_SimpleTest/Raige_Two_packed.blend");
BinaryExporter exporter = new BinaryExporter();
exporter.save(s, new File("test.j3o"));

Now the Problem is that this .j3o is nearly un-editable because it's quite laggy where as you get ~350 FPS when simply extending the upper code by rootNode.attachChild(s);

What is it that this model has to bug out sdk's. Can you guys even reproduce that?
Raige_Two_packed.blend.zip

Note: Just because the Model is uploaded here doesn't give anybody the permission to use it in their games or something ;)

Start with the attached Raige_Two_packed.blend model and reproduce the issue using the shown assetManager.loadModel and BinaryExporter code. Compare loading and editing behavior between SDK 3.0 and 3.1 alpha5, including the triangulation-error logging and CPU usage. Done means the model no longer causes the reported hang or severe lag, or the failing subsystem is identified with a reproducible diagnosis.