When I browse a slow file system in explorer (say, via adding to favorites), UI freezes for significant time (10-20 seconds and more). This occurs when I try to expand a node.
Thread dump (see attachment) shows that a sniffing resolver works in the AWT thread. I believe this is incorrect.
Created attachment 94582 [details]
AWT thread dump
This one will be harder to solve. Leaving for later version.
My current idea is to display dummy node and later replace it with real one (with icon, properties, actions). I am not sure how reliable that is going to be. I am working on a less-blocking-189979-and-181300 branch at
There is a builder at
I tried to delay call to Dataobject.find and do it later from non-AWT thread. The code seems to get far more fragile and I am afraid to do that.
So rather then fixing, let's try some defence: How often this happens? How much files your directories contain? What is their mime type? What are their extensions? Can you genereate self-profiling snapshot?
Btw. when you browse the same directory in Files tab, is it as slow as in Favorites one? If not, then I know what to solve...
No cooperation, no fix.