TC hangs when refresh network drive

Please report only one bug per message!

Moderators: Stefan2, white, sheep, Hacker

AdrianB1
Junior Member
Junior Member
Posts: 11
Joined: 2010-04-19, 08:39 UTC
Location: Bucharest, RO

Post by *AdrianB1 » 2012-06-10, 15:14 UTC

I got the same problem since version 8 beta 22 (I haven't use any older betas of ver. 8) and it is still present with the current last release.

I can reproduce it every time on my computer, there is no problem on my brother's computer that is using an older version of TC (7.something). On the computer I have both have Win 7 x64 and I am running 64 bit TC. When I open \\Network it takes a very long time to display anything (if I do anything TC freezes) or forever, this depends. Network is IPv4 only with a couple of dozens different devices, including computers with Windows, FreeBSD, routers, TV, WD TV player, audio receiver etc.

If it help in any way, my way to get TC back working is to close it and get to wincmd.ini and delete the current folder, then restart TC on C drive; this will not make the network run, but at least I can use it for local drives.

More info:
- Left history looks like this:
0=::{208D2C60-3AEA-1069-A2D7-08002B30309D}|\\Network (WORKGROUP)\
- if I map a drive and assign a letter it works opening it in an instant
- browsing the network from Explorer works fine, it takes maybe 10 seconds to display all devices (WIndows PC's very fast, FreeBSD always last)
- browsing the network with TC from my brother's computer works fine, a bit slow but nothing too bad

joker
Junior Member
Junior Member
Posts: 20
Joined: 2006-04-05, 10:42 UTC

Post by *joker » 2013-03-27, 11:25 UTC

I don't understand why it's possible that Total Commander hangs at all when accessing network drives.
In my opinion the refreshing should run in a separate thread which should definitely NEVER be able to lock the main thread.
It's a shame when Total Commander is locking up because of a very slow network path and it's even more a shame that the refreshing process cannot be aborted with ESC!!! :evil:

BullFrog
Junior Member
Junior Member
Posts: 54
Joined: 2011-06-20, 10:51 UTC

Post by *BullFrog » 2014-11-15, 14:24 UTC

Up, still a problem

skyd
Junior Member
Junior Member
Posts: 9
Joined: 2010-03-15, 23:16 UTC

Post by *skyd » 2015-03-25, 22:18 UTC

Same behavior with v8.51a on Win 8.1 64-bit.
Not doing anything special - just going to Network and then WORKGROUP.

I'm only reporting now, but am experiencing this issue for a very long time already.

Is there any way to boost priority on this one?

a110011
New Member
New Member
Posts: 1
Joined: 2016-04-14, 19:54 UTC

Post by *a110011 » 2016-04-14, 20:05 UTC

Network: 100/1000 Mb
Clients shares from: Samba (on Debian, Arch and Ubuntu), Windows 7, 8.1, XP Embedded
Accessing shares from Windows explorer work without a fail, browsing local network works. But whenever i try to access \\Network (Workgroup) TC freezes and nothing works but to kill it from task manager. I think this should be priority one bug to fix it.

User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 36232
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) » 2016-04-18, 09:49 UTC

Have you tried a newer version of TC? 7.5x is very old.
Author of Total Commander
http://www.ghisler.com

joker
Junior Member
Junior Member
Posts: 20
Joined: 2006-04-05, 10:42 UTC

Post by *joker » 2017-02-08, 10:34 UTC

v9.0a
The bug is still present. Never fixed. Always the same, for everyone who has to work on slow network shares.

Allow me to repeat the question: Why don't you allow your users - who partly also buy your software for real money(!) - to abort hanging network requests by pressing the escape key?

User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 36232
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) » 2017-02-09, 11:13 UTC

Which requests do you mean? Virtual folders like \\server or real directories like \\server\share?

In TC9, the reading of virtual folders like \\server is now done entirely in a background thread and can be aborted.

Reading of \\server\share is partially done in a background thread: FindFirstFile is called in background, but FindNextFile and FindClose are not. This is usually OK because normally the network doesn't go down in the middle of reading a directory. But if that happens, FindNextFile will hang.

TC has to call the read loop in the foreground because the content plugins which have to be called for some custom columns are not guaranteed to be thread safe.
Author of Total Commander
http://www.ghisler.com

joker
Junior Member
Junior Member
Posts: 20
Joined: 2006-04-05, 10:42 UTC

Post by *joker » 2017-05-04, 04:54 UTC

ghisler(Author) wrote:TC has to call the read loop in the foreground because the content plugins which have to be called for some custom columns are not guaranteed to be thread safe.
Now it is clear. Thanks for the explanation. I hope this can be improved in the future.

Post Reply