Yes, Chrome's implementation is extremely buggy and is triggered by all sorts of small movements, in addition to providing terrible clues to the user about what is going on.

Safari's implementation is much less painful, is only triggered when I really want it, and provides sufficient visual clues about what's going on.

Chrome's blunder is almost enough for me to switch to Safari, which is saying a lot given my preference for Chrome otherwise.