I was running into the same issue, with react-virtualized 9.22.5, it seems that the problem has been fixed in v9.22.6