Comment 2 for bug 521370

in the comment above I stated:

As you will see, when testing other situations, for one of these find()'s that are not successful, there are up to 4 screen captures reported. Normally its only one, which is what one expect.
I found the reason for that myself:

A find() in the standard is waiting max 3 seconds for the pattern to come up on the screen. This is an implicit wait(). If you know what should be on the screen, it boosts performance if you use

setAutoWaitTimeout(1)

that hinders find() after a not-found to wait for some aliens to help the screen to come up with the image we are looking for.

Normally you would think, that setAutoWaitTimeout(0) would be the way to say "don't wait at all", but there seems to be a bug, because if you use 0, the <try: except:> does not work any longer.

See full activity log