Yep, I can reproduce the problem but I'm not aware what triggers it. Maybe the JS changing the iframe's src makes a new history record in Chrome.

I'll have to investigate this further.