Bug: Files stops responding while loading network share content

[littleboot]

Description

Files gets stuck / unresponsive or crashes when a network share is not available.

If it gets just stuck it will show an "Network folder error" after a while, this timeout is way to long.
Its the same behavior for windows explorer, would be great if this can be fixed in Files by reducing the timeout.

Steps To Reproduce

Have a network folder like an SMB share.
Disconnect from network.
Try to access the network folder.

Requirements

• To make it crash click on other tabs while it is trying to access the drive that is not available.

Files Version

3.2.2.0

Windows Version

10.0.22621.3155

Log File

debug.log

[Josh65-2201]

Thanks for the report, I've added the crash while waiting to the project board.

Windows file system has to be used to get the contents of the network drive and the timeout comes along with it. Files can not change that.

[CaCTuCaTu4ECKuu]

@Josh65-2201 I already mentioned this problem but was dismissed. Even Windows Explorer doesnt work so poorly with network shares
Interaction with network SHOULD NOT freeze app as a whole, it should lock interaction with tab (folder/content) and do work in background

And even more to that look
It is trying to load every single file in location to display icons
Good luck loading few GBs with that speed while APP is unresponsive

I'm coming back to this app and every time it's just not usable itself not to say as replacement of Windows Explorer

[littleboot]

Yeah it is a shame, I really like the app but switched back to the default explorer for now, The app continues to improve every time I check so I hope I can make this my main explorer in the future

[mat-heidemann]

Had to switch back to Windows Explorer because Files became unusable due to crashes involving SMB.

[Josh65-2201]

@littleboot @matheidemann Is this still an issue on v4.0.11 https://files.community/download