Found a bug in the snapshot cleanup process with different browsers

I am using TN 24.10 RC1. Cant upgrade to final at the moment because I have a snapshot replication running for the next couple of hours.

I have one pool with some datasets on it. And I have a lot of automatically generated snapshots of these datasets, most of them are 0B.

I am trying to clean up snapshots, because the amound of snapshots grew up to 4000 and I received a note of TN that this to much and could possibly result in problems.

And yes, I found problems in the snap delete process, but I noticed this with 4000snap and I noticed it when i deleted the half of snap.

I started to clean up my snaps over the Web-UI. I noticed that my browser got slower and slower after I deleted some pages with 100 snaps each. My whole 64GB of memory was full with the TN session when I noticed that the web UI was to slow to use it. I killed the firefox process and restarted the purge of snaps.

I played around a bit to understand why this happens. I found out that when I leave the Items per page set to 50 all the time and select only one page and press the delete button, firefox constantly consumes only 1-1,5GB of ram and the delete process is finished in a shot time.

But after setting the Items per page to 100 and select one whole page for a delete operation, the ram consumption of firefox instantly grows to 5GB in the moment I only select the 100 items. But its getting worse: When I start to delete a whole page of 100 snapshots, the ram consumption of firefox just fills the complete 64GB again and is insanely slow.

While a delete operation of only 50 snaps takes 30-60sec, the delete process of 100 snaps takes up to 5-10minutes. And if its finished, the ram consumption of firefox is still 50GB.

I have found that this problem is more likely to occur if you open the snap delete menu, select 50 snaps of a page (until now, the Ram consumption is very low), then set Items per page to 100 (ram usage still low, the first 50 snaps are still selected), then select the other 50 unselected snaps of the page with the “select all” checkbox (now, the ram consumptions instantly grow to 1,5-1,6GB) and if you now delete the whole page, the ram consumption instantly grows to 50-64GB and takes a lot of time.

I noticed this with Firefox 131.0.3 on a win11 machine and updated to latest version (132.0).

I can reproduce this problem also with Brave Version 1.71.118, but the process of brave crashes after some time when ram consumption grows to much.

2 Likes

Sorry, typo. I am using 24.10 RC2, not RC1.

I wouldn’t be surprised that the GUI isn’t lean when it comes to drawing and updating elements that are part of a massive list.

Even with Core, manually managing snapshots (in the GUI) is noticeably buggy.