Closed tomavos closed 1 month ago
Name | Link |
---|---|
Latest commit | cea19b94cd2bf33c2350de821c74f38c8980cf00 |
Latest deploy log | https://app.netlify.com/sites/reselect-docs/deploys/669e7cb1ff5f5700083e6007 |
This pull request is automatically built and testable in CodeSandbox.
To see build info of the built libraries, click here or the icon next to each commit SHA.
This PR contains the following changes:
weakMapMemoize.ts
to check if thelastResult
is aRef
before dereferencing it.Context:
The previous code could leak a
WeakRef
if the dereferenced value wasundefined
(which I think happens when the original object is forcefully garbage collected): LetlastResult
be aRef
toundefined
:With this new change, we will return the new value (even when the old garbage collected value would've passed the
resultEqualityCheck
and would've been memoized).I chose the
instanceof
check becauseRef
is defined above as aWeakRef
if it is available, else it is aStrongRef
which is a locally defined class.I tried to add a unit test which reproduced the issue by garbage collecting values in the cache so they would be
Ref
s toundefined
, but I didn't have any luck. I followed a similar strategy to this test by using aFinalizationRegistry
. I also tried a test whichunmount
ed a React component containing the original state. Please let me know if you have any ideas for this unit test :)(aside) How we discovered the issue:
weakMapMemoized
array).weakMapMemoized
result got garbage collected.shallowEquals
resultEqualityCheck
(Object.keys(WeakRef{undefined})
==Object.keys([])
==[]
)WeakRef
into the code which expected an array, and caused an exception.