I discovered that almost all of my reminiscence was in use on my 8GB M1 Mac Mini (2020), and sought to extend the swap (I’ve 6-8GB swap allotted on linux, and this got here with solely 3GB in keeping with htop, which was round 80% used with a couple of functions open: TIDAL, VSCode, Firefox, Godot). The system was not truly working gradual so far as I used to be conscious. I’m working macOS Sequoia 15.5, a principally recent set up with solely a dozen or so apps put in, as I’m principally working off laborious drives.
And so I naïvely adopted this Apple neighborhood put up, which claimed that I ought to run diskutil apfs eraseVolume VM -name VM -role V (hereafter: The Sketchy Command) within the terminal in restoration mode claiming that “swap ought to now (hopefully) be permitted to develop past 8 GB giant if it ever must”. In restoration mode diskutil checklist stated that disk3s6 had “consumed” 20480 B (20.5 KB). After working the sketchy command above and rebooting (reboot straight on the terminal in restoration mode, as root, possibly that is why?) htop confirmed 0KB/0KB swap.
In my previous expertise (with Intel Macs, no thought if this could nonetheless be relevant) merely going into restoration mode and again out once more makes MacOS reassert itself and fixes points however this time it did nothing. I don’t thoughts going again to 3GB swap however 0KB doesn’t depart a lot margin.