Seva wrote:crashing and freezing is a problem
Crashing, I found to be related to running program with unresolved dependency. As a precautionary measure, before trying program for first time I would
and afterwards resume
If neglected to do this, and if still there was keyboard response, would do same command from console. This seemed to do the trick in KDE. Don't know equivalent in other DE.
Reduce possibility of there being an unresolved dependency by running
Code: Select all
ldd /Path/to/File/<binary> | grep "not found"
Code: Select all
usm -d /var/log/packages/<package of interest>
Freezing, I encountered early on. Having only 1GB of RAM, every now and then the hard disk would go for a whirl, a couple of minutes during which nothing could be done. Finally traced to slocate
, which I have shut down ever since via rootcopy
entry. Only occassionally use find
, so overhead of a prolonged find
would present no problem, however in practice the time taken for all the deep find
s can be counted in seconds.
Now, freezing only occurs in my setup when browser runs into a site with a buggy script. It's not only when using the browser directly, but also could be many minutes after using browser, and deep in the middle of some other app when freezing occurs. Reckon this is due to the nature of the system, that a script will very quickly rip through ram, and then thrash the hard disk swap partitions. Am able to retrieve situation via magic SysRq
will get rid of process gobbling up memory. Please refer to Links here: Newcomers favourite links and commands: porteus and linux
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB