Bj_rn wrote (2022-01-23):

Why reboot? Isn't the lost memory freed after binkd has been
terminated?

Well, if that was the case, I wouldn't regard it as leakage.

On a modern mainstream OS, the mess is cleaned up after the application has been terminated, but it's still called memory leak.

No, it isn't. Can it be some cache grabbing that isn't done correctly?

I've always thought it was related to the badly written WinAPI calls for cache usage, but then I saw someone else mentioning it, so I thought I'd bring it up. As I said -- no big deal.

What do I know about Windows ... ;).

The support hotline would suggest to upgrade to the newest version and try again.

2:203/2's binkd is 7 years old.

* Origin: Birds aren't real (2:280/464.47)