8290
« Last post by mouser on January 03, 2014, 01:00 AM »
Hi veriod, and welcome.
It's an interesting theory, however let me throw a bit of a wrench into the mixture.
Screenshot Captor turns the icon red before it begins its various steps of capturing a screenshot, and then turns it back when it finishes.
What that means is that when the icon sticks red for a bit, and then turns blue after a delay, it means that for some reason it took an unusual time to do the steps taking the screenshot -- not necessarily that the delay was in flashing the icon. Does that make sense?
There are two two main alternatives to consider:
The first is -- does the delay in capturing the screenshot only ever occur once, if you haven't used SC for many hours -- and then not occur again until you stop using it for many more hours? (or does the delay go away if you go and change the option in SC to "stay in memory longer")? If this is the case, then the delay happens because after a long period of disuse, MS Windows may swap Screenshot Captor memory out of physical ram and it may take a while to wake up -- or because the disk drive where SC is saving the screeenshot has gone to sleep.
Alternatively, as your post suggests, it happens even if you are using SC regularly, and it happens when your mail app is checking -- it might very well be that your mail program is triggering some events that are dominating the cpu. This might even happen because a firewall or antivirus tool is jumping in. If that's the case then it wouldn't be just SC that it would have this delaying effect on but any other application. I have noticed on my XP machine that some network slowdown events (i think caused by my software firewall) can actually cause a multisecond pause in every application trying to read the disk drive.
I would very much like to hear if you can narrow it down and definitively blame the pop mail checker (or an antivirus or firewall or network effect).
If you can cause this problem to happen very regularly, then i could try to send you a special debug version of SC that would log lots of events and could help us narrow it down.
Another way to check if the problem has to do with blocked disk access, would be to temporarily go to the "Miscelaneous Tweaks" tab and check the "Don't Auto Save Captures" option. That will avoid the automatic save-to-file step so if the delay is due to disk writing that would solve the problem.
Recent Posts
