Google chrome doesn\'t behave the same as other browsers when encountering this nugget:
I had a similar issue to this, and solved it by adding an HTML tag (in my case
) before each flush.
My guess would be that Chrome waits for an element which is being displayed to close before triggering a re-render. That's only a guess though.
It didn't seem to require 1024 bytes - I think I would have had just under 512 bytes when it worked.