Run-time error: 380 Invalid property value

[undupit]

I often get this error:
Run-time error: 380 Invalid property value
How to solve?
If I do the compare in many chunks (starting at only looking at the largest files, then going down in filesize) instead of one go, it often helps. But that takes a _lot_ more work and time, days instead of hours.

If I google the error, it sometimes points to a database problem. Under button Database, I do not have 'Use database...' selected. I think it uses a database anyway, but of an other type.
Could there be an overflow in (the size of) the database when doing a large compare? If so: how about giving the program 10x more space and giving the program 10x more space for each internal database field? I have 128 GB interrnal memory, that should be enough ...
I think I saw a similar problem arising if a video file has too many 'chunks' because the video file is damaged, making a field with data of the video, overflowing.

[Administrator]

We need the complete bug report to help you with this error.

What version of AllDup do you use?

[undupit]

We need the complete bug report to help you with this error.

What version of AllDup do you use?

4.5.64 PE.
Next time doing a large compare, I'll check if I can set log options and create a log.

[therube]

And just what type of search are you performing?
And what settings are you using for that search?

[undupit]

And just what type of search are you performing?
And what settings are you using for that search?

File content, Byte by Byte compare. Match 100%.
No options ticked under Byte by Byte. Block size etc: 32768, and other defaults.
Search options: all unticked, except CPU to low priority.
Archive files: do not extract if larger than 0 bytes.
Database: Use database... = unticked. File filter: not used. Exclude: smaller than 10 kB.
Folder filder: exclude recycle bin, c:\windows, and other default exclusions.

I did not see a way to enable logging other than what is does by default, or change the settings. Is that correct, there are no (special) (debug) settings?

[therube]

(Not that I know about such things) but on reading "invalid property", so I'm thinking you're gather "properties" (meta-data) from say picture files, & something there is causing the issue.

But given that you're just doing a plain jane content search, then you'd think, well the above thought then doesn't make sense.

So google (& again I don't know if it applies) but points out things like "controls" & "sizing"...
What causes this error? "Runtime error 380: Invalid property value"

So... maybe it could be something like you've got a "4k" monitor & ... (I'm just throwing stuff out ).


Anyhow, at what point in time does the issue manifest itself?
Not when you simply open AllDup, but at what point in the process?

[undupit]

(Not that I know about such things) but on reading "invalid property", so I'm thinking you're gather "properties" (meta-data) from say picture files, & something there is causing the issue.

I don't use meta-data search options.

Anyhow, at what point in time does the issue manifest itself?

At the step where the byte-by-byte comparisons are made.

If I click on log, I see there are _no_ entries added. So, the program exits without writing anything to the log.
The last entries visable, are from when the program _did_ succesfully a dupe search run.

I still suspect it's some kind of overflow, built-in limits, maybe too many stuff/entries written to the comparing database, being the database in memory, not on file.
Therefore (my PC is probably powerful enough), i'd like to see a version of AllDup which can hold (10x) more data / larger data fields.
Or maybe there is somewhere an integer being used, so it overflows at 2^15 (32768).

[undupit]

I'm out of ideas.
Do I have to give up?