Most applications using quick sync are working on a small amount of video for a limited amount of time, like a couple hours worth of 1080p or 4K @ 24 FPS. And then they close. So a leak could go unnoticed. Blue Iris will push that much data through Quick Sync in a matter of minutes and just keep on going.
Here's the strange thing. With a normal memory leak, memory usage goes up and CPU usage is basically unaffected. However in my experience this problem is just the opposite. CPU usage goes up and memory usage only rises a little before you end up having to restart Blue Iris. So I'm hesitant to even call it a memory leak. I really don't know what is going on.
One thing is clear: It can be resolved for most CPU models by changing to a known-good version of the media SDK. Unfortunately this doesn't tell us for certain that it is a problem with Intel's drivers/media SDK. It could just as easily be an issue with Blue Iris that just happens to only arise with certain Intel Media SDK versions. Either way, the only person who can really diagnose this issue is Ken and as far as I know the issue might not even be on his radar.
Here's the strange thing. With a normal memory leak, memory usage goes up and CPU usage is basically unaffected. However in my experience this problem is just the opposite. CPU usage goes up and memory usage only rises a little before you end up having to restart Blue Iris. So I'm hesitant to even call it a memory leak. I really don't know what is going on.
One thing is clear: It can be resolved for most CPU models by changing to a known-good version of the media SDK. Unfortunately this doesn't tell us for certain that it is a problem with Intel's drivers/media SDK. It could just as easily be an issue with Blue Iris that just happens to only arise with certain Intel Media SDK versions. Either way, the only person who can really diagnose this issue is Ken and as far as I know the issue might not even be on his radar.