Its more complicated than you might think. Having swap available means the OS can page out infrequently used memory pages. That leaves more physical memory available for active tasks. If you had lots of tasks that were idle 99% of the time, you wouldn't want them taking up real memory would you? There are various parameters that are easily set to tune how its done.
I do like and will continue to use Linux with GNU userland (or even the few Linux distros with BSD userland), just no more Raspbian. The bug is one that I have only seen in Raspbian, not in other distros.jamesh wrote: ↑Wed Dec 19, 2018 10:25 amPlease file a bug on our github tracker.
Although I suspect this is an upstream issue rather than specific to Raspberry Pi. It's also very obscure, so hardly surprising its not been seen or detected.
As for the swap thing, that almost certainly a kernel issue and nothing to do with us.
If you don't like Linux, don't use it.
You have a very "ego centric" view of the world. I've been writing X code for > 30 years and didn't even know that Xkill existed until today.
No help at all. What distribution does that web page refer to ? Does it apply to Raspbian ?
Code: Select all
pi@pi0:/proc/sys/vm $ ls admin_reserve_kbytes drop_caches oom_kill_allocating_task block_dump extfrag_threshold overcommit_kbytes compact_memory laptop_mode overcommit_memory compact_unevictable_allowed legacy_va_layout overcommit_ratio dirty_background_bytes lowmem_reserve_ratio page-cluster dirty_background_ratio max_map_count panic_on_oom dirty_bytes min_free_kbytes percpu_pagelist_fraction dirty_expire_centisecs mmap_min_addr swappiness dirty_ratio mmap_rnd_bits user_reserve_kbytes dirty_writeback_centisecs nr_pdflush_threads vfs_cache_pressure dirtytime_expire_seconds oom_dump_tasks watermark_scale_factor
A few years back I might've used xkill now and again, but nowadays it's something I need with vanishing rarity. Most X window managers correctly close a program if you hit the close button. It may take a few seconds, it may prompt you, but it does close almost every time. Anything past that usually needs a logout or restart, as the WM itself is failing.
TBH, I am quite capable of looking it up, but that still doesn't negate the fact that I had never heard of it, although, clearly, I have now. I quote "This program is very dangerous, but is useful for aborting programs that have displayed undesired windows on a user's screen.". Sounds like a nuke from orbit it's the only way to be sure type of command, but useful to know it exists. I'm not surprised this issue has not been seen before, I suspect very few people use it.