Author
Topic: Index error in Screenshot Captor (Read 2073 times)

It all started when I saw the jagged-edged screenshot on ImgBurn.com and tried to create something similar with Screenshot Captor. I browsed through the frames and masks, then saw the Clipart button and took a peek. I got a few index errors, then when I closed SC it said there had been two crashes.

I downloaded a new portable version of SC and ran it to see if my .ini was causing it. At first I didn't see the problem, so I copied the default .ini file to my portable installation and not only did I get the error, but afterwards SC wouldn't close, even with several Process Explorer and Task Manager kill attempts. It was using very little CPU, but my machine was acting really slow. I discovered it was doing around 3MB/second of disk usage (I may have hit the Rescan Dirs button at some point) at which point I restarted Windows.

I believe the default window size forces the toolbar into 2 columns, and I have only seen the error when the window is a large enough for a single column toolbar.

Returning to my original question, I think the imgburn.com image was made with TechSmith's Snagit, but if there was a similar frame or mask then it could be used with SC, apart from the drop shadow that goes along with the jagged edge.

Here's a recording so you can see exactly what I did to get the error.

And here are the two problem signatures in case they're of any help in diagnosing the problem.

Update: Watching the screencast was super useful - I'm pretty sure I know this error that triggered as you were scrolling the frame panel on the right hand side. Portable users have reported when scrolling that clipart/frame browser very quickly it can crash. I suspect you are seeing the same exact bug (whether you are running it portably or not). Seems like I really need to fix that bug.