When to use LockManager.request() across tabs instead of in-memory locks

When the same origin can start the same short, side‑effecting job from more than one JavaScript context — two tabs, a tab plus a worker, or multiple workers — an in‑memory mutex is already too small. Each context has its own heap and its own copy of any boolean, promise, or singleton, so module‑...

Source: [Dev.to](https://dev.to/chriserodriguez/when-to-use-lockmanagerrequest-across-tabs-instead-of-in-memory-locks-3350)