Same loop here. The link that was posted for the known glitch is marked SOLVED - but of course it's not really.
