GPU memory leak with HEVC hardware decoder when draining and sending MFT_MESSAGE_NOTIFY_END_STREAMING message about media-foundation HOT 2 CLOSED

Hello bluetarpmedia,

Calling ProcessMessage with MFT_MESSAGE_NOTIFY_END_STREAMING followed by MFT_MESSAGE_COMMAND_FLUSH does not follow the order of calling ProcessMessage while tearing down the MFT described in the Basic MFT Model .

Could you try by following steps 4 - 8 in the Process Data section within the processing loop of the file you had linked.

from media-foundation.

Thanks for your reply @RohitAthavale. If we remove END_STREAMING and insert END_OF_STREAM before the DRAIN as suggested in steps 4-8 then there is no leak. (Likewise there is no leak simply by removing END_STREAMING; that is to say, there is no need to add END_OF_STREAM to avoid the leak.)

We don't need the ability to send either END_STREAMING or END_OF_STREAM messages. But we noticed that sending END_STREAMING after the drain and before the flush causes this memory leak with the HEVC hardware decoder with some HEVC video streams, and also does not happen with the AVC hardware decoder, which made it appear to be a bug.

from media-foundation.