Description
Even if the tab is closed/deleted and the related BrowserViewModel is cleared from the cache, it stays around in the memory (a leak). One of the reasons, I have found so far, is that it's easy to put a class into Swift UI's @Environment, but there's no easy way to take it out from there (so far I haven't found a solution for that).