Quoting Carlos E. R.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
El 2019-02-04 a las 15:37 -0000, Dave Howorth escribió:
On Mon, 4 Feb 2019 13:20:20 +0100 "Carlos E. R." <> wrote:
Whenever I try to debug problems like this I find it can be helpful to ssh into the machine with the problem as soon as it is started,
I tried. It did not connect.
Then investigate that problem first! If you boot a machine and cannot immediately ssh into it then there's something seriously wrong. (Unless it hasn't finished booting or sshd isn't enabled, of course). The whole point is to establish the ssh connection long before any problems arise.
You misunderstand. Of course I can connect normally when the computer is normal. I can not connect when things are going on.
You are saying to leave the ssh running for weeks till it happens? Uff. I can not guarantee it.
Firefox is the default version that comes with it:
MozillaFirefox-60.4.0-lp150.3.30.1.x86_64
Desktop is XFCE.
FWIW, I'm using the same OS and FF but run LXDE.
I have two machines that started having problems after upgraded to 15.0.
Other possible variables are any add-ons you use in FF and the video hardware and drivers. I'd suggest running without add-ons, or at least only a few basic ones, and using the most basic video driver that works.
Happens on two very different computers. One laptop, one desktop. One Intel, other nvidia, one 4 gig, other 8 gig.
No, this is not hardware related. This is a fault of the kernel, how it mishandles swap into a dead embrace.
The kernel doing a poor job of handling out of swap space is not new. I find it dangerous to let swap get more than about 1/3 full. Beyond that, something is using or leaking memory that will become fatal in a few hours to a day or two. Both Chromium and Firefox leak memory. When I find swap space exceeding 1/3 full, I kill the browser, and restart it as needed. Jeffrey -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org