You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This corrects an oversight in the disposal flow on set overwrites.
We don't call dispose when creating the BackgroundFetch, because of
course, the thing hasn't been replaced yet.
And we don't call dispose when _replacing_ a BackgroundFetch, because
that isn't a value, it's just a potential value, so we abort the fetch
and forget about it (which is a no-op if the set() in question is the
resolution of that BackgroundFetch).
The missing piece is that we *do* have to dispose() the
`__staleWhileFetching` value on that BackgroundFetch promise, if there
is one, when overwriting a BackgroundFetch.
Fix: #309
0 commit comments