Bug 283528 – Web locks is not released after page navigated / refreshed

• Status: NEW
• Component: New Bugs

After a page unload, the web locks (navigator.locks) do not released correctly

## Quick Reproduce

Open a new window, open the console, check the "Preserve log", and open https://imsingee.github.io/safari-web-worker-behaviour

In chrome, the output will like

```
[load] Current locks: {held: Array(0), pending: Array(0)}
[after request] Current locks: {held: Array(1), pending: Array(0)}
====== REFRESH PAGE ======
[load] Current locks: {held: Array(0), pending: Array(0)} (<- should be empty)
====== END ======
```

But in Safari, the output will like

```
[load] Current locks: {held: Array(0), pending: Array(0)}
[after request] Current locks: {held: Array(1), pending: Array(0)}
====== REFRESH PAGE ======
[load] Current locks: {held: Array(1), pending: Array(1)} (<- NOTE: not empty)
====== END ======
```

the `Current locks` should be empty after refresh, but not

[Karl Dubost]

Created attachment 473326 [details]
rendering in safari, firefox, chrome

Safari:
held: [{clientId: "35fe0531-64b2-4c97-8a02-a0e063e1e764", mode: "exclusive", name: "lock1"}] (1)

Firefox:
{ held: [], pending: [] }

Chrome:
{held: Array(0), pending: Array(0)}


Safari Technology Preview  207           20621.1.4.3
Firefox Nightly            134.0a1       13424.11.17
Google Chrome Canary       133.0.6851.0  6851.0

[Radar WebKit Bug Importer]

<rdar://problem/140399284>