Slow captures


I recently posted about making a looping version of ‘’. I got it working and ran it, but I ran into a new problem. I’ve noticed before that the capture software goes slower as it takes more traces, but I figured that it would be solved by creating a new project in every loop. The thought process was that it would do something similar to reopening the application (which seems to make it run normal speed). As you may have guessed, it doesn’t speed it up at all and the diminishing returns make it crawl so slow I would rather eat my shoe.

Does anyone have any ideas what may be happening? Since it fixes when I restart the application I assume it is something to do with memory?


Hi Chris,

Sorry to hear about your shoe.

I’m seeing this on my end too. After 5000 traces, CWCapture turns into molasses. It also keeps a lot of memory in use. I’ll put this on the to-do list - there must be a good way to speed things up…