RyanThaDude
21 discussion posts
The past few weeks I've been giving the app (and my keyboard) a touture test with a lot of data that I'm trying to process. On idle after an hour of usage I notice ClipboardFusion's CPU and memory usage will rise over time. CPU usage can go well above 15% on my AMD 3900X 12-core/24 thread CPU and memory can go well above a gigabyte. The app will lag during usage and become unresponsive when accessing any settings via the tray icon for well over 20 or more seconds. When the app becomes like this I have to close it, wait about a minute, then re-launch for it to become "just like new" once again. Sometimes I have to force close it and re-launch as it never responds.
I've cut back the history to 16 in hopes to reduce memory, which I can't say it's helped. Right now, I have the memory trimming setting set in Advanced to help with memory but still seems to increase, just not as big as if it was at its default setting.
Main usage is clipboard scrubbing and a couple macros (mainly type-paste).
• Attachment [protected]: ClipboardFusionDebugInfo.zip [27,786 bytes]
Sounds like there could definitely be a leak there somewhere. How many times would you estimate you run the macro before it starts having a noticeable impact?
Interesting! We'll do some testing here with the Play Sound action in a Trigger rule. Thanks for posting what you found out!
What was the file type of the file you were using in the Play Sound action? We haven't been able to reproduce this issue here with a .wav file.
RyanThaDude
21 discussion posts
Quote:
What was the file type of the file you were using in the Play Sound action? We haven't been able to reproduce this issue here with a .wav file.
Sorry it took so long to reply. Was on holiday for the Christmas break.
I've attached the .wav file.
• Attachment [protected]: Tock.wav [9,800 bytes]
Ok, I was able to reproduce this issue here. It wasn't the sound file specifically but it does appear to be related to LAVSplitter. I'm seeing the same thing as you, with a new LAVSplitter thread showing up on every play of the sound file.
We'll put this on our list to investigate for the next version.
Thanks!