Solved KDE crashing on 2GB RAM, kernel doesn't handle OOM right

1000005260.gif
 
A classic moment from programming history; somewhere on an insignificant mote of dust, hanging in the outer spiral arm of a lesser known galaxy, at approximately 13.79 billion years since the hypothesized 'big bang', THIS infinitesimally improbable event occured:-

View: https://youtu.be/qXAubRZ-qjw?t=210

"it's probably something very simple... so why is it not terminating...? It really ought to work!" 😁
 
I hate to break it to OP, but OP's metal is just not enough to run the latest and greatest softwares like KDE and Firefox. It's gonna be a rather clunky game of tradeoffs of what OP is willing to live with. Up-to-date stuff that will run on OP's metal is gonna be missing features that are important to OP, and it won't be the easy and convenient stuff that everyone knows. I've been down that road, I do have old hardware that I played with in my past.

I know what it's like to have the choice of being up-to-date, cheap, fast. Choose two, you can't have all 3.
 
I must admit, being told to delete the entire freebsd installation in order to run at the original clock speed is a bit extreme 😂
Perhaps this is a feature of the new timeline, since CERN performed the Higg's boson experiment?
 
loveydovey said:
I kind of want to stick with firefox because I have all the preferences tuned for in in user.js...and also I guess it works on another machine.
Click to expand...

I'm not asking you to change your browser. I am suggesting testing with a different browser to see whether you also get segfaults.
 
Well, it's irrelevant now. I think this desktop computer is haunted. BIOS is acting completely not to specification. I just flashed it too, and nothing's changed. It was reporting weird frequency levels, now it's completely not reporting frequency levels.

Is there anything to be done except flashing BIOS in such a case? Other than that, it's probably the source of symptoms I was observing. If there were some clock mismatches of some sort happening, it could've corrupted memory...
 
You must log in or register to reply here.
Back
Top