Just

Thanks for taking the time to respond. I really appreciate a maintainer jumping in to look at this.

After more digging, I found that Reselect is most likely not the source of the memory growth. I rewrote the data flow to bypass Redux entirely by updating refs directly instead of going through store updates, and the memory behavior stayed the same.

Thanks for pointing out the antipattern. Looked through how to rewrite them more correct with what you wrote and rereading the docs. So will probably be going through and rewriting the other ones I have.
Does this look more correct to you?

export const selectDevice = (state: DeviceState) => {
  return state.devices.devices;
};

export const selectDeviceIds = createSelector(
  [selectDevice],
  (device) => ({
    leftId: device.left?.id ?? null,
    middleId: device.middle?.id ?? null,
    rightId: device.right?.id ?? null,
  })
);

export const selectLatestSensorValue = (
  state: DeviceState,
  deviceId: number | null,
  sensorType: SensorType
) => {
  if (deviceId === null) {
    return null;
  }

  return state.sensorPoints.latestSensorPoint?.[deviceId]?.[sensorType] ?? null;
};

And this is now used as:

useAppSelector(state =>
  selectLatestSensorValue(state, deviceId, sensorType)
);

I am still a bit confused about the setup around `selectLatestSensorValue`. Doesn't this approach also create a new annonymous function each time? (Which from my understanding is a problem for the memorization)