Unable to select / transform anything in the UI after exporting a collection

[keyschain]

What are you trying to do, and what do you expect to happen?

Export a collection and continue to work in the file.

What happens instead?

Seemingly the interface becomes completely unresponsive.

I have a file I started working on in the last update, opened it in the new one, made collections and added models / folders to it.

One is visible the other two are hidden, exporting the first or second doesn't cause anything, exporting the third one so far has caused the interface to lock up. It seems to vary with which export it happens, but every single time its after exporting a collection.

Model format in which the issue occurs

Java Block/Item

Blockbench variant

Program

Blockbench version

4.12.1

Operating System

Windows

Installed Blockbench plugins

No response

[JannisX11]

Are you exporting the collection to the Block/Item format or another one?
Any errors in the console? Help > Developer > Open Dev Tools > Console tab.

[keyschain]

Yeah I'm exporting to block/item, and usually it happens when its a hidden collection. Many errors afterward. I just tried it again on 4.12.2. I'll attach the log. It does end up exporting the file correctly and everything, it's just that the UI becomes unresponsive to clicking. I can still pan around and move pop up windows, but not close them or change anything in the 3d view etc.
And restarting fixes it every time, and doesn't corrupt the file or anything either.

-1737407620584.log

[JannisX11]

Were you using the Undo Selection setting? If so, this should be fixed via d766cd1
cc @Cubouse

[Cubouse]

I was, I have not gotten the bug again since my report.

[Bitslayn]

I have information on this bug. It happens with some collections, and is easy to reproduce. When you click on an affected collection at all, you won't be able to click on modelparts in the outliner, save by doing ctrl + s, or switch tabs. That instance becomes essentially useless until you reload the application completely.

It is easy to reproduce this issue if you have a lot of collections, and the collection itself will be prone to having this issue. I'm unsure what causes the particular collection to do this but the collection which did have this issue has modelparts and meshes.

This occurs on 4.12.2 Desktop for Windows