Well, I do have a problem with AppVMs completely hanging out on me on situations where firefox demands a large amount of ram and these are such cases: 1. Running a resource-intensive web application i.e. node.js web editors like Wix and Weebly 2. Downloading large files from mega.nz (I think the magic here involves loading the file into the RAM after it has been completely downloaded by the browser which is why when the browser prompts saving the file, the process is almost instantaneous... unless you don't have enough RAM to accommodate the demand. 3. Plenty of media-playing tabs open in Firefox or Chrome
There may be other cases that I have forgotten but on all cases where an AppVM froze on me, the total RAM eaten by dom0 hardly ever shrunk for it to be allocated to the AppVM, which should be expected given the existence of https://www.qubes-os.org/doc/qmemman/ I was able to get myself a workaround for the problem before, and that is making more swap, ideally within the 8GB-10GB range. However, a ram stick just died on me this week and I badly need all the RAM that I could get. Even right now, my dom0 is actively using just about 940 MB worth of RAM... which is why I think it would be best if I could permanently allocate 2048M to dom0 instead of 4096M for my case. ...Not unless there are big security-related reasons as to why 4096M has been the default on dom0. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e2856dbf-120b-4044-b3bd-59a7857477dd%40googlegroups.com.
