You appear like a coder padawan and you are mistaken. You may think you have found the culprit - most likely you have not.
You - as developer - should know how easy it is to create code which can leave enormous amount of garbage in system memory. Such garbage is usually hung processes left running without the promise ever returning or processes indefinately looping consuming more and more memory until system is exhausted and no more swap is available.
So your finding is in reality a bandaid and does not solve the real issue your code is causing.
to clarify more, these random frezzes nearly made me crazy as it happens at pure random
i love manjaro kde
i dont remmeber exactly but i think i never had random freezes with windows with this pc . only manjaro kde is installed now on ssd nvme
i tried many kernels
i tried disable compositing
i tried disable timeshif or reduce the frequency of backups
i tried also manjaro gnome, i like it but i cant use it much because it doesnt 100% supports hibernation like kde, with gnome i had freezes but i cant tell the reason. but now with terminator i had no single freeze lead to pc totally crash . i experience some times plasma lags but the pc does not totally crash like with konsole
i did not remove konsole, i only unpin it from the panel and i dont use it
Think about it - if there really was such issue with konsole - it would have been screamed out on a variety of forums including the apps source code repo.
From what you say the issue has been following you everywhere … across kernels, across various system settings - you even tried reducing your snapshots?
Instead of looking at your code you are looking at the system?
While system regressions certainly happens - I really don’t think a wildly used virtual console app like konsole is the cause of your intermittent freezes - it is more likely infinite looping deadlocks in your code.
I know - I have sometimes blamed systems - but to my own displease - I have always found it to be my code - so instead of gaffa taping your code - blaming the system - and using another terminal emulator - an emulator which is evidently better at handling deadlocks - you should implement logging and log everything until you pinpoint the issue.
I have an issue bugging me at the moment - I have been blaming Firefox browser - until I stripped down my css and html and found the browser does it right - but for some reason - and only with Firefox - never chrome based browsers - my code fails to behave as expected when formatting the pages for printing.
I could blame the browser - but it is not there - it is my code somewhere - I just have to find it.
Not so long ago I was involved in a discussion on stability.
I don’t think an efficient system exist - unless you build it ground up the Arch way.
If you choose any distribution you are presented with an initial layout defined by the philosophy driving the developers.
Stability has a different meaning dependinng on who you ask.
Plasma has never been stable for me - perhaps because I didn’t knew enough.
A couple of months ago I started experimenting - adding kwin to lxqt.
The experiment went well - and I thought - let me try the plasma desktop and I added the necessary components - and that went well too.
The key to a somewhat stable system is to have just enough components to achieve your workflow as adding more increases complexity and with increased complexity comes a degree of instability as there’s more components in play.
The amount of pressure you put on your desktop also adds a degree of instablility - especially with browsers - on a developer machine - if you are not very careful in coding your web apps - you can create a service worker which will crash your system without warning.
You mention several browsers with numerous tabs open - how many of them is running a worker service script in the background?
I see you changed the title of the topic - I am pleased I made you think - keep thinking.
In my experience - It is rarely the system itself that fails - but how it is used - perhaps strained - which makes it misbehave or crash.
after long hours googling “input/output error” i think that the problem is related to power management because i remember i got freezes many times directly or a couple minutes after waking from idle ( screen off). waking from hibernation works for hours though
i loaded defaults values in bios, maybe i changed something and i forget about it
in archlinux formum, some user had random freezes issue and fixed it by replacing wireless card
before kernel 5.0, i had to install
to be able to use wifi and bluetooth, but after 5.0 i dont have to install that package because wifi and bluetooth work after clean install of manjaro with kernel +5.0
do i have to install that package even wifi and bluetooth work without issues ?