View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001837 | Double Commander | Logic | public | 2017-05-14 21:07 | 2022-10-21 14:02 |
| Reporter | CryHam | Assigned To | Alexx2000 | ||
| Priority | high | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Projection | none | ETA | none | ||
| Product Version | 1.0.0 (trunk) | ||||
| Target Version | 0.9.0 | Fixed in Version | 0.9.0 | ||
| Summary | 0001837: Freeze on entering unreachable network paths | ||||
| Description | This is a major issue for me. It happens when I try to enter an unreachable network path in DC. E.g. \\192.168.1.2\ or any other network path that doesn't exist or is now unreachable (e.g. PC turned off, network unplugged). Most importantly it happens when I have previous tabs with such paths (and those are now inactive) and accidentally switch to them (not knowing or remembering). Also happens if I enter such paths from Directory Hotlist (Ctrl-D). And lastly when I just type a command like cd \\192.168.1.2\. In all 3 cases DC freezes (does not respond) for at least 50 seconds! Right now it is hopeless. My usual reaction is open task manager and kill DC process. I can do that in like 3 seconds. It'd be best to somehow check if remote path is reachable. Best in own thread to not block DC at all. Allowing switch to other tabs, tabbing to opposite view, and working normally. If such check isn't possible, then wait for maximum 2 seconds (maybe could more in a thread). And if it didn't work, just ignore the path completely. Marking it also as unreachable so any next try wont waste time again. | ||||
| Tags | No tags attached. | ||||
| Fixed in Revision | |||||
| Operating system | Windows | ||||
| Widgetset | Win32 | ||||
| Architecture | 64-bit | ||||
| related to | 0001037 | closed | App hangs after a network drive was disconnected | |
| related to | 0001494 | closed | Timout and cancle key like ESC for unavailable paths | |
| has duplicate | 0002135 | closed | Program hangs for long time when selecting tab of unreachable network share | |
| related to | 0002160 | closed | Application won't start with unavailable network drive |
|
|
The issue most hopeless when I quit DC on a tab that has a remote path. Then the path becomes unavailable, e.g. remote PC is turned off. Now when starting DC, it won't show up at all, for about 1 minute! There is no easy way of fixing this. Only way I know is to edit doublecmd.xml. Does anyone have an idea how to fix this? Or at least where to look in sources? |
|
|
A possible solution could be (before accessing any paths): - find \\ in path, this means a network location - start a ping command - check its result after 1 sec, it will say if the location is reachable |
|
|
I think I've fixed it, I tested all cases and it works now. Turned to be way simpler than I thought, just used DirectoryExists. Could you look at the diff here: https://github.com/cryham/doublecmd-test/commit/a0cfabe104a9bd03e735e733c7df6231caf4bd24 and see/test if it is okay, and if so then add it to svn? |
|
|
Okay found a bug already, I can't change dirs in archives. |
|
|
I guess that it also will not work if network share requires user/password. |
|
|
You can abort operation by "ESCAPE" key now. Also if loading in background thread enabled then freeze only one tab now. |
|
|
This is not resolved. Actually, it happens all time around and renders entire app unusable if you map network path to drive letter and you move out of the network (or network dir stays active on restart when network is not there). For measure, I personally had it ocurring anywhere from several times per day to several times per week. The behavior is consistent across machines (Windows 10) and users. I and my group of 5 people all switched from TC to DC last yeear, and after several months of usage everybody reverted back to TC for this reason solo, otherwise people were pretty happy with DC. The problem happens less often without network involved, but network operations have all kinds of problems, not just freezing. |
|
|
Since this one is closed and this is old bug tracker, issue can be tracked at https://github.com/doublecmd/doublecmd/issues/183. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-05-14 21:07 | CryHam | New Issue | |
| 2017-06-05 12:11 | CryHam | Note Added: 0002278 | |
| 2017-08-02 09:12 | CryHam | Note Added: 0002312 | |
| 2017-12-10 22:58 | CryHam | Note Added: 0002412 | |
| 2017-12-10 23:29 | CryHam | Note Added: 0002413 | |
| 2017-12-11 07:31 | Alexx2000 | Note Added: 0002416 | |
| 2018-09-24 09:44 | Alexx2000 | Relationship added | has duplicate 0002135 |
| 2018-09-24 09:46 | Alexx2000 | Relationship added | related to 0001037 |
| 2018-09-24 09:47 | Alexx2000 | Relationship added | related to 0001494 |
| 2018-10-25 09:01 | Alexx2000 | Relationship added | related to 0002160 |
| 2018-10-27 22:06 | Alexx2000 | Note Added: 0002841 | |
| 2018-10-27 22:06 | Alexx2000 | Assigned To | => Alexx2000 |
| 2018-10-27 22:06 | Alexx2000 | Status | new => resolved |
| 2018-10-27 22:06 | Alexx2000 | Resolution | open => fixed |
| 2018-10-27 22:06 | Alexx2000 | Fixed in Version | => 0.9.0 |
| 2018-10-27 22:06 | Alexx2000 | Target Version | => 0.9.0 |
| 2020-03-20 21:46 | majkinetor | Note Added: 0003422 | |
| 2020-03-20 21:47 | majkinetor | Note Edited: 0003422 | |
| 2020-03-20 21:48 | majkinetor | Note Edited: 0003422 | |
| 2020-03-20 21:48 | majkinetor | Note Edited: 0003422 | |
| 2022-10-21 14:02 | DoubleTim | Note Added: 0003845 |
