Recently I found that my page crashed when data set increases(about 2000 items, and 1k per item),
visual(size and remain together) was just 50, but the memory use was nearly 1G.

And the finite live demo performs similarly. Maybe it's a memory leak, or a memory waste, simple 100,000 items retain 64M default , and 150M maximum after scrolling up and down.

50 'keeps' size and all vnodes default, more vnodes and vueComponent are created but not deleted after.

I think it should be a memory waste, virtual item vnodes and components have references with VirtualList in this way. When data set increases, it maybe a memory problem.

<VirtualList :size="50" :remain="6" :bench="44" class="list" :start="startIndex">
    <Item v-for="(udf, index) of items" :index="index" :key="index"></Item>
</VirtualList>

Solution is quite simple, pass pure data and the itemComponent to the container, and create vnodes what we need VirtualList, which can cut down references across objects.

<VirtualList :size="50" :remain="6" :bench="44" class="list" :start="startIndex"
    :items="items" :item-component="itemComponent" :item-binding="itemBinding">
</VirtualList>

See more detail at changed and the example 'finite-m' ,
for comparison, the new way saves memory indeed ~