This behavior is usually caused by tabbing out and back in to
Duelyst on Chrome. This background throttling when Duelyst is not
the active tab is an issue with Chrome itself, and not something we
have much control over when running in the browser. Try popping out the Duelyst tab into its own window. This usually
helps let Chrome know "hey, I want this window to keep processing,
there's an important match going on over there!"