koniec1980
Given that you're describing the behaviour in the same way each time ("freezing") but that it fixed itself multiple times until it didn't, I think Zanir is almost certainly correct: This isn't a game "bug" (though the way it's coded to to group and process calculations might be more or less efficient, leading to lesser or greater processor/memory demand).
It's just a large number of interactions that your device can't track, and ultimately spins its wheels trying to calculate. It may function better on another device or it may need optimization from CG to run on any device. We've had situations like this before that later improved (hundreds to thousands of DoTs when playing Tuskens used to have a more negative effect on play than it does now), so it's possible that at some point in the future an update will put in some more optimized code that runs this particular interaction fast enough not to get stuck on your device. But generally the "fix" in the short term and possibly even in the long term is that the player has to buy a faster device.
I know it sucks. I remember that feeling with the Tuskens. But you can also try to avoid this particular interaction now that you know it doesn't work on your machine.