opening netork drive directory closes Explorer++

Found a bug or something that needs fixing?
Post Reply
nlcarter
Posts: 4
Joined: Thu Aug 27, 2015 10:37 pm

opening netork drive directory closes Explorer++

Post by nlcarter » Tue Sep 03, 2019 7:06 am

I'm using version 1.3.5.531 and recently stumbled across an issue where opening a large (330GB) directory on a network drive (Synology NAS) and waiting for the folder sizes to be calculated caused the program to simply close. This was repeated several times. Bummer!

I then downloaded the latest dev build, 1.4.0.831, and got the exact same result. Hmmm...

My system is Windows 10 x64 and both Explorer++ versions are 64-bit.

Any help or suggestions?

Thanks!

Janus
Posts: 34
Joined: Fri Aug 05, 2016 9:03 am

Re: opening netork drive directory closes Explorer++

Post by Janus » Thu Sep 12, 2019 12:52 pm

I would start with how many directories/files are in it.
Next would be the directory level.
Grab the free version of treesize and take a good look at it.

Walking the dir tree takes time, lots and lots, of time.
It also takes memory, lots and lots, of memory.
Both things that your os wants to keep to itself.

Windows on off as I think of it after a friend named it that way, behaves badly with proper win32 api programs.
It is an appliance front end for your M$ cloud account, {wait until you have to pay monthly to have a desktop}, not intended for use outside the walled garden of the app store.
It is also a moving target API wise, and inherently unstable as a result.

I use my own custom fork of explorer++ which I have modified for how I work, including integrating void tools everything for calculating dir/tree sizes while browsing.
I am not done working out all the bugs yet unfortunately.
I only have 10M or so files to keep track of, but it works well enough for me.


Janus.

Post Reply