sybok
But after 15-20 minutes of use, and while using only firefox with one tab,
Periodic monitoring is a good tip, though I’d prefer one that stores the output in a (set of) file(s) for later inspection after a possible freeze.
f='~/Monitored.txt'; :> "${f}"; while true; do <monitoring command> >> "${f}"; done
The monitoring command could be a sequence of commands (each command with its redirection):
echo "" >> "${f}"; date >> "${f}"; free -h >> "${f}"; df -h >> "${h}"; sleep 5
or something more sophisticated.
I think that ‘watch sensors | tee <output file>’ would not perform well as I have an experience with ‘tee’ that stored the output “in blocks” (after the command is finished) which I suspect is not what you would want.
Apart from the above suggestions:
1) I had issues with Firefox used on an antiX installed on an AMD Ryzen CPU desktop.
Firefox froze|crashed my X-server.
Sometimes, I was able to Ctrl+Alt+Fn to a TTY and start a console session to solve it without reboot, sometimes reboot was necessary.
I’ve never solved it, it just went away (hopefully never to return) with some updates, I guess.
2) Running out of disk space or RAM (both could be caused by caching)?
It might be caused by size of the LO document and web-page(s) opened in FF.
Xunzi_23 posted tips to set up browsers to tame cache use (and while-exit cleanup).
3) See also a recent topic concerning wi-fi connection and ConnMan: https://www.antixforum.com/forums/topic/misterious-problem-when-i-net-conection/
4) A creepy HW issue indicating a glitch or a pre-fail state (e.g. HDD|SDD).
EDIT: Added sleep in the example (sequence of) command(s)
- This reply was modified 7 months ago by sybok.