Hello Jack, > Hello, I've started using Sculpt OS and the integrated Falkon web > browser. It frequently crashes when I have several tabs open, I > believe this is because the ram it has been assigned is too small. I > couldn't seem to find any mention of how to edit the ram allocated to > processes in the Sculpt OS documentation? > > How do I dynamically edit the allocated ram to processes such as the > Falkon web browser? When I am using the Leitzentrale and I click on > the Falkon web browser, I can see it shows 1.95 GiB / 2.00 GiB, I am > guessing this is the allocated ram? However I am only assuming this is > the allocated Ram size as it does not specify what type of storage > this is, i.e Hard Drive Storage or Ram Memory.
At the moment there is no out-of-the-box user-interface to change the RAM or CAP quota for deployed components and changing them currently involves some fiddling as you need to adjust the resource allowances manually. In this case it is especially involved as the 'falkon-jemalloc' pkg bundles mulitple components running in an statically configured sub-init. That being said, generally speaking, you can change the quota by adding a 'ram' and 'caps' attribute to either a '<start>' or '<launcher>' node and increase the value. That is one of the reasons where creating a launcher comes in handy as sometimes the pre-configured resource requirements might not be enough in all cases and one needs to override them. As you noticed that is true in particular when using the falkon pkg as its resource consumption is quite volatile depending on the website and number of tabs. Of course Genode itself contains all the means for reacting to such resource requests dynamically (and this already employed for certain components, like the 'depot_rom' or 'ram_fs') but is not enabled in general to prevent components from tipping on each others toes. How to better make use of available slack-resources is still ongoing research. > […] > > I will need to do more tests to see if the audio not working was a > fluke or I was doing something incorrectly before. On most systems the current audio driver can only be started once as the device might not produce sounds when the driver was restarted. Depending on the system you might get away by starting it several times until it is audible again but that is not always a given. Unfortunately switching presets might implicitly start and stop the driver and is best avoided (after the initial exploration or try-out phase of course) and for regular usage of Sculpt I would recommend making a preset persistent (as discussed in the documentation) and to mainly work with launchers. We will work on remedy this limitation but there is not time-frame for that yet. Regards Josef -- Josef Söntgen Genode Labs http://www.genode-labs.com/ · http://genode.org/ _______________________________________________ users mailing list -- [email protected] To unsubscribe send an email to [email protected] Archived at https://lists.genode.org/mailman3/hyperkitty/list/[email protected]/message/VOIT6EGMUNFDPUZRBTAFKV2TTGH4VCDG/
