Imatch 2023.8 crashes when changing preferences

[Mees Dekker]

I've downloaded and installed IMatch 2023.8. All seems fine (apart from ribbon sizes, see https://www.photools.com/community/index.php/topic,14130.0.html). But the moment I change something in the preferences, IMatch crashes.

I then get a message that a dunp file will be created, but that file is never produced or completed. Can't find it anywhere.

Imatch is in debug mode, logfile attached.

[Mario]

Windows may take several minutes to produce the thumb file, depending on the memory size and other things. IMatch uses an external helper tool to wait for Windows to finish producing the dump and then shows this message: The Debug Dump File

Nothing unusual in the log file, except some warnings about invalid hotkey entries for some keys in your resource file:

Code Select Expand

03.26 14:58:20+  47 [9EFC] 01  4 Unknown key combination while processing hotkey 'Cursor links'.
03.26 14:58:20+    0 [9EFC] 01  W> Unknown key combination while processing hotkey 'Cursor rechts'.
03.26 14:58:20+    0 [9EFC] 01  W> Unknown key combination while processing hotkey 'Thuis'.
03.26 14:58:20+  16 [9EFC] 01  W> Unknown key combination while processing hotkey 'Einde'.
03.26 14:58:20+    0 [9EFC] 01  W> Unknown key combination while processing hotkey 'Cursor omhoog'.
03.26 14:58:20+    0 [9EFC] 01  W> Unknown key combination while processing hotkey 'Cursor omlaag'.
You may want to check the resource-nl.json file.

IMatch reports that the last session did not shut-down correctly. Did IMatch crash before you started it again?

I see a warning from the experimental IMatch performance monitor about drive P:
Windows fails to report performance data for this drive. What kind of drive is P:? Mapped network drive? USB disk? VeraCrypt or Cryptomator disk?

[Mees Dekker]

The point is that the message about debug-dump does not come up.

And yes: Imatch indeed crashed before a new start.

P: is a mapped network drive (on a NAS).

I'll send you an updated/corrected resourcefile via e-mail.

[Mario]

After displaying the crashed / DUMP file message, IMatch asks Windows to produce the DUMP file named "imatch.dmp" in the TEMP folder on your computer. And when this succeeds IMatch launches an external helper utility from the same folder IMatch resides in named "PTDebug.exe".

If Windows fails to produce a DUMP file in the TEMP folder (no disk space, virus checker interfering) this will not work.
Do you see a file named "imatch.dmp" in the TEMP folder on your system? Enough free disk space (about the same size as the memory installed)? Virus Checker?

From the IMatch perspective, asking Windows to produce a DUMP file is the only thing it can do when it crashes. No logging or user interaction are available anymore. So I have no info if Windows succeeded to create the DUMP file, or when not, WHY not. I don't think this has happened before, or at least not as far as I recall.

P: is a mapped network drive (on a NAS). 

That explains that. Disk monitoring functions in Windows don#t work with network shares or drives. I'm still working on that and to monitor network usage instead in this case. All a work in progress.

[Tveloso]

In case it helps, I do not experience a crash here, when changing Preferences.

I changed the the Import XMP Face Regions flag, under Edit->Preferences->Metadata2 from No to Yes, saved the change, and then went back and changed it to No again, and did not have a crash with either change.

[Mario]

Thanks. Helpful.
I don't experience any crashes with this on two computers and I've tried all the pages...
Maybe Mees remembers which settings page is active when it crashes. Without DUMP file this is almost impossible to analyze.

[Gerold Neeb]

Same behavior here. IMatch crashed after changing preferences. I will send an email with a dump file.

[Jingo]

Same for me too.. I was modifying the Ribbon Height just to see what it would do and received the error message.

[Mario]

The 3rd party user interface toolkit was not happy when IMatch uses ribbons instead of their toolbars and crashed when processing the "global options changed" event generated when Apply was pressed or the preferences dialog was closed at just the wrong time.

I have fixed this for the next release.