What steps will reproduce the problem?
1. Launch app.
2. Wait (or not...not sure how long it takes, but it consistently does so).
3. Take a look at activity monitor.
What is the expected output? What do you see instead?
Comskip consistently takes over 2 gigs of Virtual Mem, even when not in
operation and just idling in the background. Something seems wrong with that.
Shouldn't it take very little Virtual Mem when idling?
What version of the product are you using? On what operating system?
Newest version from website on Snow Leopard with 8gigs total ram.
Please provide any additional information below.
Original issue reported on code.google.com by i...@elephantwriters.com on 15 Oct 2010 at 9:28
Original issue reported on code.google.com by
i...@elephantwriters.comon 15 Oct 2010 at 9:28