Crash when updating multiple files' properties

[samid]

The following sequence of actions sometimes causes an access violation in TC v7 RC1:

- go to a directory with several audio files (flac in my case), select several of them;
- right click to get the context menu and click Properties, or just Alt-Enter to get the properties dialog;
- in the properties tabs, I have the "ID-Tag" tab added by dbPoweramp (http://www.dbpoweramp.com/dmc.htm), which allows to view/update tags such as "artist", "album" etc. on audio files; so I go to that tab to change e.g. the album title;
- I try to paste the new album title (copied from elsewhere) into the album field in the "ID-Tag" tab.

At that point a crash occurs ("Total Commander ... has encountered a problem and needs to close"), see screenshotImage: http://dima.softmaster.co.uk/test/Clipboard01.jpg and Image: http://dima.softmaster.co.uk/test/Clipboard02.jpg.

Actually, I also came upon the same problem using version 6.54a, and now it happens with 7 RC1. I think this is a problem in TC as I tried doing the same (changing multiple files' properties via the ID-Tag tab) in regular Windows Explorer, and did not see any problems. Another piece of data that may be a lead is that sometimes such an operation (changing the album name on multiple files) succeeds but after that, the property pages for any files can no longer be shown from within TC (i.e. nothing happens if I select "Properties" from the context menu or Alt-Enter on a file) - I have to close and restart TC to revive that ability.

FWIW, I can also provide stack traces captured by selecting the "debug" option from the Windows crash popup. If any other info/experiments are needed please let me know.

(Off the top of my head, I would guess that this might be caused by TC trying to asynchronously refresh files' data while the tags on the files are being updated by the ID-Tag but of course I might be wrong; this is just a guess.)

Thanks.[/b]

[ghisler(Author)]

Unfortunatrly this address isn't in Total Commander itself. It's difficult to say whether it's in that ID3-Tag tool, or in some other shell extension. You can try ShellExView as described in many other threads here to find the problematic shell extension.

The problem is that some shell extensions assume that they are only called from Explorer, and then try to access some Explorer internals which simply do not exist in Total Commander...

[samid]

I understand. But can't you in TC catch such exceptions and not crash (possibly showing a dialog with the info about the error)?

[ghisler(Author)]

It depends - if the exception occurs in the main Total Commander thread, then it will be caught by my exception handler. Howerver, many Explorer addons create their own threads, and it's not possible to catch such exceptions from my code.