DigitalVolcano Software Support

Issue scan stalls because file is named /!/ Went back and renamed file to /123/ and it scanned okay

Expected behavior - A warning about inability to handle file name.

Actual Behavior

1) clicked stop -> r u sure u want to cancel scan ->yes = nothing
2) clicked stop -> r u sure u want to cancel scan ->yes = nothing
3) clicked stop -> r u sure u want to cancel scan ->yes = nothing
4) Any attempt to close triggers "open message window" warning
5) Task Manager to end task - (result below)

AppHangB1
Application Name: DuplicateCleaner.exe
Application Version: 3.0.0.4
Application Timestamp: 4f4e8cf8
Hang Signature: 34b5
Hang Type: 6400
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Hang Signature 1: 34b525759e118b5171466ee658448577
Additional Hang Signature 2: 2468
Additional Hang Signature 3: 24686ac0238b62206d31246a7e13b2c9
Additional Hang Signature 4: 34b5
Additional Hang Signature 5: 34b525759e118b5171466ee658448577
Additional Hang Signature 6: 2468
Additional Hang Signature 7: 24686ac0238b62206d31246a7e13b2c9


6) Will not close through Task Manager
7) Can not reload DuplicateCleaner with out creating multiple instances - requires syst restart
8) Will not close for restart - requires a forced system reboot
9) resolved by renaming file


supporting screen shots:
http://cdn.image-max.com/drew/dup-clean-error-ja026.jpg
http://cdn.image-max.com/drew/dup-clean-error-ja027.jpg
http://cdn.image-max.com/drew/dup-clean-error-ja028.jpg

Thanks for posting comprehensive error info. Will investigate as to why DC isn't handling this well.

What file system is this? I know NTFS doesn't allow the / character in filenames.

It is NTFS

ntfs / win 7 64 bit

ssd (apps) / raid 5 (data) (but the drive conf shouldn't make a difference)

http://cdn.image-max.com/drew/dup-clean-driv-conf-3.jpg

To follow up

The following characters are invalid as file or folder names on Windows using NTFS:
/ ? < > \ : * | ” as well as any character you can type with the Ctrl key

! is an acceptable character

I'm trying to test this but can't work out a way of forcing a / character in a windows filename. Any ideas anyone?

"Issue scan stalls because file is named /!/" (**anyname**.jpg)

May be some confusion here the file name "!" (exclamation point) is creating the problem

It appears you are referring to "/"


for clarification - http://cdn.image-max.com/drew/dc-file-names.jpg

> file is named /!/

You're calling it a "file", yet it is a directory?

> ! is an acceptable character

Right.

> can't work out a way of forcing a / character in a windows filename

Ditto.

> the file name "!" (exclamation point) is creating the problem

Shouldn't be.

> /!/

My original thought was that you were using / for emphasis, but using an ! shouldn't be an issue.

Are you sure that ! is an ! & not some character that looks like an !?
If you drop to a C: prompt, does a DIR show the directory name to be !?

I have no means to test RAID if that could play into the problem?

In this picture I have both files named ! & also directories named !! & all scan without issues.

Perhaps enable logging in Duplicate Cleaner & hopefully you will get at least a partial log prior to your hang. Even a log with the directory named ! & then also as 123 (to compare).

I've tested with file/folder named '!' and it worked fine.
So, other explanations are some sort of corruption, or maybe the /!/ folder being a junction point pointing to itself? (infinite loop)

You are correct - I said file when I should have said folder.
I am quite sure that the character is an exclamation point (!)


The work around was easy, just rename the folder (it was only a sort folder anyway)


I will rename a folder, try again this weekend, and save log results.

However, I stand the original premise that the folder name did create a problem for DC on my system, as captured in the screenshots. If It is not creating a problem for anyone else, then I would not spend a lot of time on it.

I've spent a fair amount of time trying to re-create error on my system - unsuccessfully.

While as you can see from the images I did get an error, I apparently drew the wrong conclusion as to the cause of the error. Sorry for the trouble. Unfortunately that puts me back to an unknown error.