IMatch 64 bit 2017.14.2 freezes

[jelvers]

Since some days Imatch freezes during scrolling through pics in viewer mode (F12, W). There is no way that I can close Imatch thereafter in the normal way (I have to use task manager).  When I run the database diagnosis thereafter I do not get an error message.

I never had this behaviour before. I have attached the logfile.

Regards, Juergen

[Mario]

This log file shows just a normal IMatch startup. This is not a log file taken right after IMatch stopped responding.

Since this happens only for a few days and while using the Viewer, I guess a recent Windows update has caused an issue with WIC, DirectX or your graphic card driver.
Try to update your graphic card driver via the built-in update function in Windows or see the web site of your computer manufacturer or graphic card vendor for information about the most recent version.
Also, temporarily disable your virus checker while you scroll files in the Viewer, just for a test.

If this happens again, secure the IMatch log file before you restart IMatch. Maybe we can then see some error message or somthing...

[jelvers]

Thanks for advice. Will do so...

Regards, Jürgen

[jelvers]

I have in the meantime updated my NVidia driver. Again, I got a crash during scrolling in view mode. Perhaps I should mentioned that I had also Photoshop running on the side. Haven't tried out without my Kasperky Antivirus. Will do so next.

Please find attached the logfile after the crash but before starting IMatch again.

Regards, Juergen

[Mario]

In your first post you said "freezing" (IMatch stops responding).
Now you said crash (IMatch is shutting down with a crash message and a DUMP file is generated). Different things, entirely different possible causes.
What is  it?

The log file looks normal. The last entry is from IMatch loading a JPEG file from the cache folder. No errors. No warnings.
Nothing that would indicate a crash, or IMatch no longer responding.
Maybe your virus checker is blocking IMatch?
Are you using the same files all the time? Does it happen with the same set of files? Maybe a file is corrupted? Or a file triggers the AV?

The last file loaded was

C:\ProgramData\photools.com\IMatch5\previewcache\3B1DB56B-3356-4A04-87EC-53B989E81925\91\91755.jpg

[jelvers]

In your first post you said "freezing" (IMatch stops responding).
Now you said crash (IMatch is shutting down with a crash message and a DUMP file is generated). Different things, entirely different possible causes.
What is  it?

I shoul have been clearer. It is freezing, indeed!

Maybe your virus checker is blocking IMatch?

I will check this now!

Are you using the same files all the time? Does it happen with the same set of files? Maybe a file is corrupted? Or a file triggers the AV?
The last file loaded was
C:\ProgramData\photools.com\IMatch5\previewcache\3B1DB56B-3356-4A04-87EC-53B989E81925\91\91755.jpg

I use files for one given category and tried to attach some to another category. But I can't recall whether it were always the same files. Will check in detail.

Again, many thks for your help.

Regards, Juergen

[Mario]

With obscure issues like this, any bit of information can lead to a solution.
IMatch does not seem to recognize anything unusual, until it freezes.

Please switch IMatch to debug logging (Help > Support > Debug Logging) so we can a maximum of information in the log when it happens again.

[jelvers]

Have sent the latest debug file to you by sep mail due to size. The issue seems to be related to a problem with Photoshop. When I do use PS at the same time and process pics, which I shift with the mouse form Imatch to PS then after returning to IMatch, it may freeze after a while. The last time it happened when I wanted to return from PS to Imatch (see logfile).

Nevertheless I have checked certain files and my Kasperskky AV as recommended. No issue there.

Regards, Juergen

[Mario]

Maybe PS is locking files, preventing IMatch from accessing them? Adobe software is not designed to be cooperative.

Tip: If you just ZIP your log file, you can attach even very large log files.
It's better to keep things in one place, not spreading a topic between emails and the community.

I have zipped your log file and attached it below. After zipping, from the 4MB only 240KB remain.

Still, no clue.
You wrote that you somehow edit the same files in Ps/IM, that you drag files from IMatch to PS. This may cause PS to lock files, for example...
Do you keep the Viewer open while you drag files from PS to IM or vice-versa? PS is in the habit to lock files and this may cause IMatch to be dead in the water unless Windows expires a timeout or PS releases the file lock. I use Ps and Lr with IMatch often, but I did not notice anything unusual.

[jelvers]

Do you keep the Viewer open while you drag files from PS to IM or vice-versa? PS is in the habit to lock files and this may cause IMatch to be dead in the water unless Windows expires a timeout or PS releases the file lock. I use Ps and Lr with IMatch often, but I did not notice anything unusual.

Well, I drag the files from IMatch File Window, but I haven't closed the Viewer. Maybe this causes the freezing. I will do some checking on this and come back.

Again many thks for all your advice. Great support!!

Regards, Juergen

[Mario]

Dragging files from IM to Ps involves the Windows drag & drop subsystem, and Ps will lock the files you drop when opening them. When you have the same files in the Viewer, IMatch might need to access the original file via the file system, to determine on-line status etc. I just tried but this did not produce a lock on my computer (I tested PS CC 2018 and Lr Classic).

[jelvers]

I further played around with it. It really looks as if it has something to do with the interaction between IMatch and PS. This time the viewer was NOT involved and IMatch froze after I had "shifted" some pics (in file view) from IMatch into PS. IMatch froze again.

Perhaps the following info is of use as well: When I start IMatch thereafter again it takes quite some time, until IMatch is loading again. When it's up and running it starts importing metadata (adding/updating) therafter although there are no new files.

When I do not involve PS everything works just fine.

I have attached the "freeze"-logfile, but I can't see anything unusual from it.

Regards, Juergen

[jelvers]

I forgot to mention: my Windows 10 version is: Windows 10 Vers 1709 (Build 16299.248)

Rgds, Juergen

[jelvers]

One more observation: I transfered pics via <shift><alt><enter> (opene with.....) into PS. Worked fine (at least during a period of 30 minutes). When I go back to drag and drop shifting the freezing issue occured again.

Regards, Juergen

[Mario]

No hint in the log file.

Maybe Ps somehow handles the standard Windows drag & drop wrong or locks some resources inside Windows which delay or even block IMatch. Since I have never observed this behavior myself, I cannot tell.
If IMatch starts slowly when Ps is running, either Ps has allocated so much memory that Windows has to struggle to make room for IMatch (Ps is a well-known memory hog and uses an uncooperative way to allocate memory - severely affecting the way Windows manages memory) or it maybe has files locked an IMatch is delayed by Windows running into timeouts while performing file system operations.

That IMatch is rescanning folders is normal. Ps may "touch" files in folders you use, changing the folder "last modified" timestamp or even file timestamps. IMatch has to check to find new, updated or deleted files.

[jelvers]

I think we leave it at that. It somehow has to do with PS. I haven't observed this phenomenon in the past either. At least I can open my files in PS via the IMatch <open with> option. A new version of PS may change this behaviour. I had some bad experiences re new video drivers and PS in the past. And their support is miles away from yours  .....................

Again many thks for your support.

Ragrds, Juergen

[loweskid]

This is a long shot but may be worth a try.  I had a similar problem a while ago which I eventually traced to the Adobe Bridge cache file being corrupted.  I deleted everything to do with the Bridge cache file and let it rebuild it as needed.  This cured my problem.  I suggest you search your folders for anything to do with the Bridge cache and delete them - there were files in some folders with names such as .bridgesort or similar (note the dot at the start of the file name).  You may have to set Explorer to 'show hidden files' if you haven't already.

[jelvers]

Unfortunately no success so far................

Regards, Juergen