There should be a warning like: Actual swf's size > possible bytesTotal > 0, or people will manage to get Chrome to stuck...

Maybe bytesTotal should be easier to access as well (a parameter). It's dangerous, but it's very simple for a user to find his swf size (even easier with a proper comment that tell him how). That is until building (somehow) a macro that does that for him.