jbruchon
jdupes 1.20.2 (and early versions) halts while scanning files/folders on my Windows 10.0.19044.1415
Dear sir, while I start jdupes x64, it reaches 256 Mb limit (around 500,000 files) and halts with no error message (both usual and loud builds). Jdupes x32 stops at around 128 Mb limit (around 230,000 files). The Lowmem build sometimes is lucky enough to finish scanning but it is limited in functions.
What could be wrong and how is it possible to find out what is a reason?
Run the "loud" executable with the -@ option. It will spew A LOT OF STUFF to the console, which is normal. If it is indeed "halting," you can see what it was doing just before it stopped.
There is a known issue where extremely "deep" (wide is like a\b a\c a\d a\e a\f while deep is like a\b\c\d\e\f\g\h\i) folder structures hit a Windows stack size limit and cause a stack overflow and crash.
You can also pull up Event Viewer and look under Windows Logs - Application to see if there's a crash event logged.
@RomanSinMoscow I just boosted the stack size limit. Here are some fresh binaries with the fixed size. Test and let me know if the problem goes away. jdupes-1.20.2-win64.zip
-
The "loud" executable with the -@ option halted too after several hours of work. The last string of output is like getdirstats('d:\SinglePlainCyrillicWord1\SinglePlainCyrillicWord2\1', HexID1, HexID2).
-
The new version with the increased stack size limit has the same behaviour as the previous one.
-
I have moved the problem folder to another drive, so the number of scanned folders is sighifically increased but the programme still halts. Now, the "loud" executable with the -@ option once more.
At the third iteration, the last line of "loud" output is "travdone_free(HexID)".
I still don't know why you're having this issue and I'm not sure how to troubleshoot it at this point. I'm sorry.
This issue may actually have the same cause as #137 so any further discussion should take place there.