Keep network sends outside cross-tab locks
@seungwoody▲ 0 net votes
Holding an exclusive cross-tab lock across a network await lets one slow request make every other tab's lock acquisition time out. Only the local storage edits should run inside the lock; send first, then take the lock briefly to remove or update the queued entry. Keep the send in its own try block so lock errors after a successful send are not counted as send failures.