Explorer memory growing when right click on 4.3 MKVMERGE file

[ric9887]

I am having trouble tracking down why this is happening.
I have a bunch of MKV files, muxed with various different versions of mkvmerge. However, if I right click on one writen using 4.3, then the memory indicator in task manage starts to climb until it exhausts the memory on the machine.
The only way to regain the memory it is to stop/start explorer, although I can not see with any tools that explorer (or anything else for that matter) is grabbing the memory.

This is happening on both my Windows 7 (x64) machines. If I remux a file with 2.6 or 3.4, I can right click on the file and the memory is fine.

I am not sure what explorer tries to do when you right click, and I have searched the contextual entries in the right click menu to find out what could be causing it (I have since removed MediaInfo, but it wasn't causing it)

The 4.3 mkv files play fine btw, its just the machine which gets sluggish when the memory is exhausted.

It isnt only right clicking on the file, copying it, moving it etc all create the same symtom.

I have tried removing Security Essentials / Malwarebytes.

I am still trying many things, but any pointers would be appreciated.

Regards
Rich

[sneaker_ger]

Do you have DivX installed? I heard it could cause problems with the preview on the new files with header compression.

[ric9887]

I do have DivX installed and you are right, it would appear that DivX didnt like header compression. I have yet to discover how you tell if an MKV has been mux'ed with or without header compression (although if explorer goes mad, then its a good indicator I guess)

[sneaker_ger]

If you open a file with mkvinfo you can find the information under "Segment, size xyz">"Segment tracks">"Content encodings">"Content encoding">"Content compression". It will say "Algorithm: 3 (header removal)" for tracks with header removal compression.

[ric9887]

Thats great, thanks.
I started looking at files which I knew were not muxed with header compression and that section does not appear at all in those file, but sure enough it was there when I encoded with compression enabled.

Thank you for your help.