In CoEdit:
When creating a very large amount of change events simultaneously (~100k), for example by deleting a large amount of text at once (tested with ~700 lines of lorem ipsum), coweb sends the changes and spends minutes in coalesceEnvelopes in cometd.js:369. This causes the browsertab (tested in newest Chrome for Debian) to be unresponsive for that amount of time.
Because this takes excessively long, the coweb connection dies and after that the editor no longer synchronizes anything.
(JS Error message on next event send: Uncaught Illegal state: already disconnected )
If you reload, you will see that none of the delete-events have been received on any other peer and the editor is still in its original state.
Is there a way around that?
In CoEdit:
When creating a very large amount of change events simultaneously (~100k), for example by deleting a large amount of text at once (tested with ~700 lines of lorem ipsum), coweb sends the changes and spends minutes in coalesceEnvelopes in cometd.js:369. This causes the browsertab (tested in newest Chrome for Debian) to be unresponsive for that amount of time.
Because this takes excessively long, the coweb connection dies and after that the editor no longer synchronizes anything.
(JS Error message on next event send: Uncaught Illegal state: already disconnected )
If you reload, you will see that none of the delete-events have been received on any other peer and the editor is still in its original state.
Is there a way around that?