Massive amount of rerendering introduced in v2.9.0

Since v2.9.0 the component containing the useVirtual hook gets rerendered massively, like tens of times for every pixel scrolled. Subjectively this got even worse in v2.10.0

This codesandbox logs the rerenders to the console: https://codesandbox.io/s/jovial-tesla-ii60w?file=/package.json It has v2.8.2 preconfigured, as you can see the amount of rerendering is not great even in this version, but still within reasonable bounds. Once you upgrade to v2.9.0 or v2.10.0 in the package.json the console will show you what I’m talking about.

[tannerlinsley]

We’ve recently reverted the 2.10 breaking change on master and pushed a new patch release. That doesn’t technically fix this perf regression, but it makes it within reach. @piecyk we should probably roll back the pixel-based rerendering on 2.x and figure out a better perf strategy with the other breaking changes in the next branch.

[osdiab]

I haven’t been able to make a repro trigger this in a sandbox, but with the v3 beta i am getting a maximum update exceeded error every time I render our components (unless I remove measureElement from each items’ refs), and with v2.10.4 it generally seems fine but i’m experiencing the same max update exceeded error in certain pages on our app. happy to give you access to our code if you want to try reproing it on our app.