Hi,
While using the ID-Tag (dBpoweramp 12) shell property page from within Total Commander, I very often (maybe 1 in 2 or 3 times) get access violation. This happens at different moments - usually while updating tags but sometimes when just displaying the ID-Tag page.
Edit: I initially wrote that this happens only when multiple files are selected, but that's really not the case: I tried viewing ID-Tag page for single files, and crashed on 4th or 5th file.
Here is the screenshot of the error (this time it occurred when I just tried to view multiple files' ID-Tag):
screenshot1
Here is the error detail:
screenshot2
Finally, here is the screenshot of the debug window on the error:
screenshot3
I think the selected thread is the one that caused the error as indeed it is trying to read "dword ptr [edi + 4]" and edi is 0 (and access violation is reading 0x00000004).
Finally, here is the stack trace for that thread copied from the debugger:
> ntdll.dll!7c911f6e()
[Frames below may be incorrect and/or missing, no symbols loaded for ntdll.dll]
ntdll.dll!7c910732()
ntdll.dll!7c9106ab()
ntdll.dll!7c9106eb()
ntdll.dll!7c910732()
ntdll.dll!7c9106ab()
ntdll.dll!7c9106eb()
ntdll.dll!7c913288()
ntdll.dll!7c9166f1()
ntdll.dll!7c91657e()
dMCShell.dll!0199673d()
dMCShell.dll!01994ee6()
dMCShell.dll!01973e33()
dMCShell.dll!019691a5()
dMCShell.dll!0196af0f()
user32.dll!77d54204()
ntdll.dll!7c915af1()
ntdll.dll!7c915b4f()
ntdll.dll!7c915707()
ntdll.dll!7c919a9c()
ntdll.dll!7c910732()
ntdll.dll!7c910732()
ntdll.dll!7c91657e()
ntdll.dll!7c91659e()
kernel32.dll!7c80e494()
kernel32.dll!7c80e4a4()
user32.dll!77d54204()
user32.dll!77d54204()
kernel32.dll!7c80adde()
kernel32.dll!7c80adf0()
ue32ctmn.dll!01376b03()
ue32ctmn.dll!0137557a()
ue32ctmn.dll!01374205()
ue32ctmn.dll!013741fd()
ws2_32.dll!71ab130b()
ntdll.dll!7c910833()
ntdll.dll!7c910895()
ntdll.dll!7c9284f6()
ntdll.dll!7c928528()
ntdll.dll!7c9011a7()
ntdll.dll!7c928714()
ntdll.dll!7c918f87()
ntdll.dll!7c918e74()
ntdll.dll!7c90e8c4()
ntdll.dll!7c918dfa()
ntdll.dll!7c919bd3()
ntdll.dll!7c910895()
ntdll.dll!7c919a9c()
ntdll.dll!7c919b3f()
ntdll.dll!7c919aeb()
kernel32.dll!7c80930a()
ntdll.dll!7c90d664()
kernel32.dll!7c80a6ea()
kernel32.dll!7c80a70e()
user32.dll!77d54204()
dMCShell.dll!01972223()
dMCShell.dll!0196ae0f()
dMCShell.dll!0196b18e()
dMCShell.dll!0197e918()
dMCShell.dll!019970ec()
user32.dll!77d54204()
dMCShell.dll!01997191()
kernel32.dll!7c80b683()
user32.dll!77d54204()
If any other info is needed I'll be happy to provide it.
Thanks.
While using the ID-Tag (dBpoweramp 12) shell property page from within Total Commander, I very often (maybe 1 in 2 or 3 times) get access violation. This happens at different moments - usually while updating tags but sometimes when just displaying the ID-Tag page.
Edit: I initially wrote that this happens only when multiple files are selected, but that's really not the case: I tried viewing ID-Tag page for single files, and crashed on 4th or 5th file.
Here is the screenshot of the error (this time it occurred when I just tried to view multiple files' ID-Tag):
screenshot1
Here is the error detail:
screenshot2
Finally, here is the screenshot of the debug window on the error:
screenshot3
I think the selected thread is the one that caused the error as indeed it is trying to read "dword ptr [edi + 4]" and edi is 0 (and access violation is reading 0x00000004).
Finally, here is the stack trace for that thread copied from the debugger:
> ntdll.dll!7c911f6e()
[Frames below may be incorrect and/or missing, no symbols loaded for ntdll.dll]
ntdll.dll!7c910732()
ntdll.dll!7c9106ab()
ntdll.dll!7c9106eb()
ntdll.dll!7c910732()
ntdll.dll!7c9106ab()
ntdll.dll!7c9106eb()
ntdll.dll!7c913288()
ntdll.dll!7c9166f1()
ntdll.dll!7c91657e()
dMCShell.dll!0199673d()
dMCShell.dll!01994ee6()
dMCShell.dll!01973e33()
dMCShell.dll!019691a5()
dMCShell.dll!0196af0f()
user32.dll!77d54204()
ntdll.dll!7c915af1()
ntdll.dll!7c915b4f()
ntdll.dll!7c915707()
ntdll.dll!7c919a9c()
ntdll.dll!7c910732()
ntdll.dll!7c910732()
ntdll.dll!7c91657e()
ntdll.dll!7c91659e()
kernel32.dll!7c80e494()
kernel32.dll!7c80e4a4()
user32.dll!77d54204()
user32.dll!77d54204()
kernel32.dll!7c80adde()
kernel32.dll!7c80adf0()
ue32ctmn.dll!01376b03()
ue32ctmn.dll!0137557a()
ue32ctmn.dll!01374205()
ue32ctmn.dll!013741fd()
ws2_32.dll!71ab130b()
ntdll.dll!7c910833()
ntdll.dll!7c910895()
ntdll.dll!7c9284f6()
ntdll.dll!7c928528()
ntdll.dll!7c9011a7()
ntdll.dll!7c928714()
ntdll.dll!7c918f87()
ntdll.dll!7c918e74()
ntdll.dll!7c90e8c4()
ntdll.dll!7c918dfa()
ntdll.dll!7c919bd3()
ntdll.dll!7c910895()
ntdll.dll!7c919a9c()
ntdll.dll!7c919b3f()
ntdll.dll!7c919aeb()
kernel32.dll!7c80930a()
ntdll.dll!7c90d664()
kernel32.dll!7c80a6ea()
kernel32.dll!7c80a70e()
user32.dll!77d54204()
dMCShell.dll!01972223()
dMCShell.dll!0196ae0f()
dMCShell.dll!0196b18e()
dMCShell.dll!0197e918()
dMCShell.dll!019970ec()
user32.dll!77d54204()
dMCShell.dll!01997191()
kernel32.dll!7c80b683()
user32.dll!77d54204()
If any other info is needed I'll be happy to provide it.
Thanks.
Comment