[karbomusic]

I'd look at how much memory it's actually using before saying it's a memory leak. And a memory leak shouldn't cause glitches per se but not out of the question.

To the other user's mention of unkillable process, that's not a memory leak but with the driver and kernel where reaper.exe is stuck waiting on something down in kernel that isn't there anymore (or similar). That's why it's not killable without a reboot which reboots the kernel in the OS. Also, typically writing to memory one shouldn't should result in pretty much an instant crash (access violation) or corruption that causes a crash a short time later.

Are the drivers up to date as a sanity check? I also wouldn't hesitate to think it's one of the plugins misbehaving - I suppose you could run those in a separate process (a reaper option) and when it happens again, reaper should still work but the plugin will be fubar on its own in it's own separate process.