StandardTableView leaking memory when scrolling?

[MostroW1502]

I've first noticed that when running the application in debug mode makes the tableview scroll very poorly, it slows down to a crawl when scrolling up and / or down.
The slowdown disappears when building and running the release version though.

Memory consumption increases drastically when scrolling through the rows, and it never gets freed?

It could be that i'm using the table view in an unintended manner, at this point i've got no idea.

I've written a small test case if people want / need to see the code used for adding rows to the table view.

i've tried a ListView version, but it exhibits the same kind of issue, memory usage increases.
Memory usage increases faster when scrolling slowly through the data and slower when scrolling fast through data.
Also a strange thing was that resizing the window also increases memory consumption?

Both tests are 8 columns of test data which are randomly generated u64's displayed as a hex string when sent over to the Slint side.
Test data generated is 15000 rows of data.

Looking at the component a little longer i am under the impression now that this is not a memory leak, but a virtualization problem or rather the lack of one?

[MostroW1502]

i'm a little stumped here, memory usage is quite high, as the test data takes 1.25GB of RAM once almost all rows are loaded.

the same data loaded into a datagridview in .net takes 150~175MB once fully loaded, that's quite a difference, am i doing something wrong here or is there something else going on?

[tronical]

Also a strange thing was that resizing the window also increases memory consumption?

This is a rather typical symptom on Windows, when the swap chain buffers are accounted for by the task manager (you’re looking at those numbers, right?)

What you could try is to enable the `renderer-skia’ feature. Does that help?

[MostroW1502]

Wow this is quite a dramatic change in memory consumption, i must admit.

I wouldn't have figured that switching the renderer would have this kind of impact, seems there's enough to learn from this.

To be exact, memory consumption dropped from 1.25GB to 36.7MB even way more efficient than the .net version!
The executable has increased in size though, i can live with that perfectly as disk space is pretty cheap these days.

One last question if i might ask one, is there any specific documentation you would recommend on reading regarding this?

Thank you so much!