I-Match 5.6.22

Started by er2joe, August 18, 2016, 05:32:13 AM

Previous topic - Next topic

er2joe

I just opened I-Match a couple of times tonight, and each time, when exiting the application, I got a dialog box telling me that I-Match crashed. I opened the dump file, and saw that the error was a 0x8000000c. An attempt was made to read from or write to protected memory.

Since it happened two times in a row, I attempted to open the application again, and this time, it didn't fail. Naturally, I didn't save the dump file from before, and opening up the application again erased the dump file.

Thought I'd have better information for you, but as I said, the dump file was deleted.

Joe

Mario

#1
Do you by change have installed the Windows 10 windows anniversary update?

It seems that Microsoft has introduced some bugs in that release.
I can reproduce this issue on one PC where this update has been installed. IMatch (or rather a Windows component) crashes while Windows is unloading 3rd party DLLs after IMatch has already shut-down. At this time only the Microsoft runtime code is running, unloading DLLs it has loaded while IMatch was running. And this is where the crash happens - in a Windows component named "UIAutomationCore.dll", which is part of Windows itself.

I'm currently looking at ways to find out which part of the Microsoft runtime is causing this. Or maybe a 3rd party component used by IMatch is not compatible with the latest W10 update. Or maybe it is a bug in the aforementioned Windows component.

IMatch is already closed at that time. The database is closed, settings are written, even the log file is closed. No harm can thus come from this. I hope that IMatch fixes this problem in their UIAutomationCore.dll and maybe I can figure something out. My guess is that it is caused by a 3rd party component in combination with components changed by Microsoft for this update. Which makes this even harder to track down...
-- Mario
IMatch Developer
Forum Administrator
http://www.photools.com  -  Contact & Support - Follow me on 𝕏 - Like photools.com on Facebook

Tallpics

Hi Mario

Since installing the WIN 10 anniversary update I have also been getting an error reported after IMatch closes.

A memory dump is then written.

IMatch opens normally after the error and a diagnostics reports a healthy database.

As you suggest that you have been able to reproduce this error I haven't attached the memory dump as it is very large (557,268kb) but I can let you have it if required.

I also have an IMATCH5_LOG.txt and im5diag.txt

Mario

Initial results of my analysis show that a GPF is caused in the UIAutomationCore.dll, which is part of Windows and has been updated in the anniversary update. The crash seems to happen when a 3rd party component IMatch uses shuts down. This will be very hard to solve, I've already contacted the vendor of the component.

Since IMatch is already shut-down at that time, there is no danger for the database or settings or anything.
-- Mario
IMatch Developer
Forum Administrator
http://www.photools.com  -  Contact & Support - Follow me on 𝕏 - Like photools.com on Facebook

Tallpics

Thank you for the quick update Mario.

This is reassuring as the databases aren't compromised.

With this knowledge there really isn't a problem... we just have to close the warning box :-)

Mario

#5
It's annoying, though.
I have tree computers running the latest IMatch 10 versions, and the problem shows up only on one. In about 30%-50% of the IMatch shut downs.

I have found some reports about other applications crashing in this DLL as well, and there seems to be a hotfix from Microsoft. I will need to investigate further.
-- Mario
IMatch Developer
Forum Administrator
http://www.photools.com  -  Contact & Support - Follow me on 𝕏 - Like photools.com on Facebook

er2joe

I wonder if, perhaps, it might be possible that the problem is caused by a more restrictive implementation in the module, and that the problem is actually that a call is made that shouldn't be, a call is not made that should be, or a parameter is incorrect in a call that is made? Just throwing out some possibilities that *could* be the cause, and it isn't (totally) Micro$oft's fault.

As with the other respondent, I can provide the entire Minidump, if desired. Mine is 510655460 bytes.

I *do* see that component *(UIAutomationCore.dll) listed in the Minidump. Here is the information from the Minidump:

Dump Summary
------------
Dump File:   imatch5.dmp : C:\Users\joepi\AppData\Local\Temp\imatch5.dmp
Last Write Time:   9/4/2016 11:03:58 PM
Process Name:   IMatch5.exe : C:\Program Files (x86)\photools.com\IMatch5\IMatch5.exe
Process Architecture:   x86
Exception Code:   0xC0000005
Exception Information:   The thread tried to read from or write to a virtual address for which it does not have the appropriate access.
Heap Information:   Present

System Information
------------------
OS Version:   10.0.14393
CLR Version(s):   

Modules
-------
Module Name   Module Path   Module Version
-----------   -----------   --------------
IMatch5.exe   C:\Program Files (x86)\photools.com\IMatch5\IMatch5.exe   5.6.0.22
ntdll.dll   C:\Windows\System32\ntdll.dll   6.2.14393.103
kernel32.dll   C:\Windows\System32\kernel32.dll   6.2.14393.0
KERNELBASE.dll   C:\Windows\System32\KERNELBASE.dll   6.2.14393.0
apphelp.dll   C:\Windows\System32\apphelp.dll   6.2.14393.0
psapi.dll   C:\Windows\System32\psapi.dll   6.2.14393.0
user32.dll   C:\Windows\System32\user32.dll   6.2.14393.5
win32u.dll   C:\Windows\System32\win32u.dll   6.2.14393.0
d3d11.dll   C:\Windows\System32\d3d11.dll   6.2.14393.0
DWrite.dll   C:\Windows\System32\DWrite.dll   6.2.14393.0
imanno5.dll   C:\Program Files (x86)\photools.com\IMatch5\imanno5.dll   5.6.0.22
gdi32.dll   C:\Windows\System32\gdi32.dll   6.2.14393.0
gdi32full.dll   C:\Windows\System32\gdi32full.dll   6.2.14393.0
msvcrt.dll   C:\Windows\System32\msvcrt.dll   7.0.14393.0
rpcrt4.dll   C:\Windows\System32\rpcrt4.dll   6.2.14393.82
advapi32.dll   C:\Windows\System32\advapi32.dll   6.2.14393.0
sechost.dll   C:\Windows\System32\sechost.dll   6.2.14393.0
sspicli.dll   C:\Windows\System32\sspicli.dll   6.2.14393.0
CRYPTBASE.dll   C:\Windows\System32\CRYPTBASE.dll   6.2.14393.0
IMEngine5.dll   C:\Program Files (x86)\photools.com\IMatch5\IMEngine5.dll   5.6.0.22
shell32.dll   C:\Windows\System32\shell32.dll   6.2.14393.103
bcryptPrimitives.dll   C:\Windows\System32\bcryptPrimitives.dll   6.2.14393.0
cfgmgr32.dll   C:\Windows\System32\cfgmgr32.dll   6.2.14393.0
windows.storage.dll   C:\Windows\System32\windows.storage.dll   6.2.14393.103
imgui5.dll   C:\Program Files (x86)\photools.com\IMatch5\imgui5.dll   5.6.0.22
combase.dll   C:\Windows\System32\combase.dll   6.2.14393.103
ucrtbase.dll   C:\Windows\System32\ucrtbase.dll   6.2.14393.0
powrprof.dll   C:\Windows\System32\powrprof.dll   6.2.14393.0
shlwapi.dll   C:\Windows\System32\shlwapi.dll   6.2.14393.0
kernel.appcore.dll   C:\Windows\System32\kernel.appcore.dll   6.2.14393.0
SHCore.dll   C:\Windows\System32\SHCore.dll   6.2.14393.0
profapi.dll   C:\Windows\System32\profapi.dll   6.2.14393.0
ole32.dll   C:\Windows\System32\ole32.dll   6.2.14393.0
oleaut32.dll   C:\Windows\System32\oleaut32.dll   6.2.14393.0
ws2_32.dll   C:\Windows\System32\ws2_32.dll   6.2.14393.0
imlib5.dll   C:\Program Files (x86)\photools.com\IMatch5\imlib5.dll   5.6.0.22
imsq5.dll   C:\Program Files (x86)\photools.com\IMatch5\imsq5.dll   5.6.0.22
ptgeo5.dll   C:\Program Files (x86)\photools.com\IMatch5\ptgeo5.dll   5.6.0.22
ptpicore5.dll   C:\Program Files (x86)\photools.com\IMatch5\ptpicore5.dll   5.6.0.22
ptpif5.dll   C:\Program Files (x86)\photools.com\IMatch5\ptpif5.dll   5.6.0.22
ptresmgr5.dll   C:\Program Files (x86)\photools.com\IMatch5\ptresmgr5.dll   5.6.0.22
ptspell5.dll   C:\Program Files (x86)\photools.com\IMatch5\ptspell5.dll   5.6.0.22
ptvision5.dll   C:\Program Files (x86)\photools.com\IMatch5\ptvision5.dll   5.6.0.22
mfc140u.dll   C:\Windows\System32\mfc140u.dll   14.0.24212.0
msimg32.dll   C:\Windows\System32\msimg32.dll   6.2.14393.0
winspool.drv   C:\Windows\System32\winspool.drv   6.2.14393.0
dxgi.dll   C:\Windows\System32\dxgi.dll   6.2.14393.0
comctl32.dll   C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.14393.0_none_74bc87d3d22d9abe\comctl32.dll   6.10.14393.0
urlmon.dll   C:\Windows\System32\urlmon.dll   11.0.14393.82
ToolkitPro1720vc140U.dll   C:\Program Files (x86)\photools.com\IMatch5\ToolkitPro1720vc140U.dll   17.2.0.0
msvcp140.dll   C:\Windows\System32\msvcp140.dll   14.0.24212.0
GdiPlus.dll   C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.14393.51_none_c38355ab140728f4\GdiPlus.dll   6.2.14393.51
VCRUNTIME140.dll   C:\Windows\System32\VCRUNTIME140.dll   14.0.24212.0
version.dll   C:\Windows\System32\version.dll   6.2.14393.0
msvfw32.dll   C:\Windows\System32\msvfw32.dll   6.2.14393.0
wsock32.dll   C:\Windows\System32\wsock32.dll   6.2.14393.0
winhttp.dll   C:\Windows\System32\winhttp.dll   6.2.14393.0
winmm.dll   C:\Windows\System32\winmm.dll   6.2.14393.0
wininet.dll   C:\Windows\System32\wininet.dll   11.0.14393.0
mscms.dll   C:\Windows\System32\mscms.dll   6.2.14393.0
PolyImagePro.DLL   C:\Program Files (x86)\photools.com\IMatch5\PolyImagePro.DLL   2.4.2.3
bcrypt.dll   C:\Windows\System32\bcrypt.dll   6.2.14393.0
iertutil.dll   C:\Windows\System32\iertutil.dll   11.0.14393.82
opencv_core310.dll   C:\Program Files (x86)\photools.com\IMatch5\opencv_core310.dll   0.0.0.0
imagehlp.dll   C:\Windows\System32\imagehlp.dll   6.2.14393.0
opencv_objdetect310.dll   C:\Program Files (x86)\photools.com\IMatch5\opencv_objdetect310.dll   0.0.0.0
opencv_face310.dll   C:\Program Files (x86)\photools.com\IMatch5\opencv_face310.dll   0.0.0.0
comdlg32.dll   C:\Windows\System32\comdlg32.dll   6.2.14393.0
WINMMBASE.dll   C:\Windows\System32\WINMMBASE.dll   6.2.14393.0
userenv.dll   C:\Windows\System32\userenv.dll   6.2.14393.0
CONCRT140.dll   C:\Windows\System32\CONCRT140.dll   14.0.24212.0
imm32.dll   C:\Windows\System32\imm32.dll   6.2.14393.0
uxtheme.dll   C:\Windows\System32\uxtheme.dll   6.2.14393.0
opencv_ml310.dll   C:\Program Files (x86)\photools.com\IMatch5\opencv_ml310.dll   0.0.0.0
opencv_videoio310.dll   C:\Program Files (x86)\photools.com\IMatch5\opencv_videoio310.dll   0.0.0.0
opencv_imgproc310.dll   C:\Program Files (x86)\photools.com\IMatch5\opencv_imgproc310.dll   0.0.0.0
opencv_imgcodecs310.dll   C:\Program Files (x86)\photools.com\IMatch5\opencv_imgcodecs310.dll   0.0.0.0
avifil32.dll   C:\Windows\System32\avifil32.dll   6.2.14393.0
avicap32.dll   C:\Windows\System32\avicap32.dll   6.2.14393.0
msacm32.dll   C:\Windows\System32\msacm32.dll   6.2.14393.0
tiptsf.dll   C:\Program Files (x86)\Common Files\Microsoft Shared\Ink\tiptsf.dll   6.2.14393.0
ssleay32.dll   C:\Program Files (x86)\photools.com\IMatch5\ssleay32.dll   1.0.1.8
libeay32.dll   C:\Program Files (x86)\photools.com\IMatch5\libeay32.dll   1.0.1.8
msvcr90.dll   C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.9247_none_5090cb78bcba4a35\msvcr90.dll   9.0.30729.9247
wwb9_32w.dll   C:\Program Files (x86)\photools.com\IMatch5\wwb9_32w.dll   9.30.0.82
sxs.dll   C:\Windows\System32\sxs.dll   6.2.14393.0
clbcatq.dll   C:\Windows\System32\clbcatq.dll   2001.12.10941.16384
msctf.dll   C:\Windows\System32\msctf.dll   6.2.14393.103
msxml3.dll   C:\Windows\System32\msxml3.dll   8.110.14393.0
msxml6.dll   C:\Windows\System32\msxml6.dll   6.30.14393.0
IconCodecService.dll   C:\Windows\System32\IconCodecService.dll   6.2.14393.0
WindowsCodecs.dll   C:\Windows\System32\WindowsCodecs.dll   6.2.14393.0
propsys.dll   C:\Windows\System32\propsys.dll   7.0.14393.0
dwmapi.dll   C:\Windows\System32\dwmapi.dll   6.2.14393.0
explorerframe.dll   C:\Windows\System32\explorerframe.dll   6.2.14393.0
icm32.dll   C:\Windows\System32\icm32.dll   6.2.14393.0
dataexchange.dll   C:\Windows\System32\dataexchange.dll   6.2.14393.0
dcomp.dll   C:\Windows\System32\dcomp.dll   6.2.14393.0
twinapi.appcore.dll   C:\Windows\System32\twinapi.appcore.dll   6.2.14393.0
IPHLPAPI.DLL   C:\Windows\System32\IPHLPAPI.DLL   6.2.14393.0
webio.dll   C:\Windows\System32\webio.dll   6.2.14393.0
mswsock.dll   C:\Windows\System32\mswsock.dll   6.2.14393.0
winnsi.dll   C:\Windows\System32\winnsi.dll   6.2.14393.0
nsi.dll   C:\Windows\System32\nsi.dll   6.2.14393.0
dnsapi.dll   C:\Windows\System32\dnsapi.dll   6.2.14393.0
rasadhlp.dll   C:\Windows\System32\rasadhlp.dll   6.2.14393.0
FWPUCLNT.DLL   C:\Windows\System32\FWPUCLNT.DLL   6.2.14393.0
schannel.dll   C:\Windows\System32\schannel.dll   6.2.14393.103
crypt32.dll   C:\Windows\System32\crypt32.dll   6.2.14393.0
msasn1.dll   C:\Windows\System32\msasn1.dll   6.2.14393.0
mskeyprotect.dll   C:\Windows\System32\mskeyprotect.dll   6.2.14393.0
ncrypt.dll   C:\Windows\System32\ncrypt.dll   6.2.14393.0
ntasn1.dll   C:\Windows\System32\ntasn1.dll   6.2.14393.0
ncryptsslp.dll   C:\Windows\System32\ncryptsslp.dll   6.2.14393.0
d2d1.dll   C:\Windows\System32\d2d1.dll   6.2.14393.0
nvspcap.dll   C:\Windows\System32\nvspcap.dll   2.11.4.0
setupapi.dll   C:\Windows\System32\setupapi.dll   6.2.14393.0
nvapi.dll   C:\Windows\System32\nvapi.dll   21.21.13.7254
dpapi.dll   C:\Windows\System32\dpapi.dll   6.2.14393.0
uiautomationcore.dll   C:\Windows\System32\uiautomationcore.dll   7.2.14393.0
oleacc.dll   C:\Windows\System32\oleacc.dll   7.2.14393.0
msftedit.dll   C:\Windows\System32\msftedit.dll   6.2.14393.0
duser.dll   C:\Windows\System32\duser.dll   6.2.14393.0
atlthunk.dll   C:\Windows\System32\atlthunk.dll   6.2.14393.0
coml2.dll   C:\Windows\System32\coml2.dll   6.2.14393.0
PhotoMetadataHandler.dll   C:\Windows\System32\PhotoMetadataHandler.dll   6.2.14393.0
windowscodecsext.dll   C:\Windows\System32\windowscodecsext.dll   6.2.14393.0
xmllite.dll   C:\Windows\System32\xmllite.dll   6.2.14393.0
cabinet.dll   C:\Windows\System32\cabinet.dll   5.0.1.1
d3dcompiler_47.dll   C:\Windows\System32\d3dcompiler_47.dll   6.2.14393.0
cryptsp.dll   C:\Windows\System32\cryptsp.dll   6.2.14393.0
edputil.dll   C:\Windows\System32\edputil.dll   6.2.14393.0
linkinfo.dll   C:\Windows\System32\linkinfo.dll   6.2.14393.0
policymanager.dll   C:\Windows\System32\policymanager.dll   6.2.14393.0
msvcp110_win.dll   C:\Windows\System32\msvcp110_win.dll   6.2.14393.0
dlnashext.dll   C:\Windows\System32\dlnashext.dll   6.2.14393.0
actxprxy.dll   C:\Windows\System32\actxprxy.dll   6.2.14393.0
ntmarta.dll   C:\Windows\System32\ntmarta.dll   6.2.14393.0
mssprxy.dll   C:\Windows\System32\mssprxy.dll   7.0.14393.0
ntshrui.dll   C:\Windows\System32\ntshrui.dll   6.2.14393.0
srvcli.dll   C:\Windows\System32\srvcli.dll   6.2.14393.0
cscapi.dll   C:\Windows\System32\cscapi.dll   6.2.14393.0
netutils.dll   C:\Windows\System32\netutils.dll   6.2.14393.0
dbghelp.dll   C:\Windows\System32\dbghelp.dll   6.2.14321.1024
dbgcore.dll   C:\Windows\System32\dbgcore.dll   6.2.14321.1024

Mario

Please don't just copy/paste such long lists of rubbish data in your posts. It makes them unreadable on mobile devices and also fills up the community search engine with nonsense. Always save to a text file and just attach to your posts. Usually I would extract the text from your post, save it to a text file and attach. But not this time.
-- Mario
IMatch Developer
Forum Administrator
http://www.photools.com  -  Contact & Support - Follow me on 𝕏 - Like photools.com on Facebook

er2joe

Point taken.

So, here is the same information in a text file, and another text file that contains the call stack. As you can see from this, in my crash, IMatch was still running.

Mario

Thanks, but I already know where the crash happens. It crashes in the cleanup code of a 3rd party library. I know how I can work around it, but I'm still investigating the reason of the crash. It only happens on W10 with the 201607 update.
-- Mario
IMatch Developer
Forum Administrator
http://www.photools.com  -  Contact & Support - Follow me on 𝕏 - Like photools.com on Facebook

er2joe

Got (what appears to be) this crash again, but this time, I wasn't exiting the application. The Support Helper dialog popped up requesting that I send the problem report in, but it is 146MB. Based on the previous discussion, I'm betting you don't want the problem report.

Am I right?

Joe Pizzi

Mario

Joe, are you using the most recent version of IMatch (5.7.2)? This version does not have this problem anymore - at least as far as I know.
-- Mario
IMatch Developer
Forum Administrator
http://www.photools.com  -  Contact & Support - Follow me on 𝕏 - Like photools.com on Facebook

er2joe


Mario

If you did get a crash that's not during (after) shut-down, it's something different.
First thing would be to try if you can reproduce it. If not, it's less severe.

Attach or send me the log file first (it's in the ZIP created by the IMatch crash handler). This will tell me if it's useful to look into this. Or, if you have some sort of cloud space, upload the DUMP ZIP where I can download it.


Crashes happen for a tons of reasons, and in many cases, a crash is not reproducible because it is caused by a dozen things which went south in just the right moment...
-- Mario
IMatch Developer
Forum Administrator
http://www.photools.com  -  Contact & Support - Follow me on 𝕏 - Like photools.com on Facebook

er2joe

Well, it certainly hasn't happened the two or three times I've opened I-Match since.

Here is a link to the .zip file: https://www.dropbox.com/sh/cd9j6pu2x5xy3sv/AAATD9u6mhCGECmNroqGwCIYa?dl=0

Mario

Thanks. I have downloaded the log file and I will analyze it over the weekend. Maybe I can figure out what the problem is on your system. Always tricky.
-- Mario
IMatch Developer
Forum Administrator
http://www.photools.com  -  Contact & Support - Follow me on 𝕏 - Like photools.com on Facebook