Re: Lindows programs unexpectantly closing
- From: goarilla <kevin.paulus@xxxxxxxxx>
- Date: Fri, 29 Jun 2007 17:37:59 +0200
Oldtech wrote:
Stefan Patric wrote:no problem there although i would set max user processes to anything elseOn Thu, 28 Jun 2007 23:21:56 +0200, goarilla wrote:My results are here as an example:
Pete wrote:You didn't indicate what programs and their versions, or what version of Lindows. Is it any program or just the browser? Does the OS crash or does the GUI or is it just the apps? How often does it do it?I am having a problem with Lindows programs unexpectedly closing. Justmy best bet would be that you have ( memory or max nr of user processes
DISAPPEARING! This most often happens while using my web browser. Has
anyone else encountered this, and found a fix or at least what the
problem is?
) limits in place
check ulimit -a and /var/log/messages, if your programs hit those limits
they get killed
Also, after an app dies, type 'free' in a terminal. See, if your swap is max'ed. You could have a memory leak. Also, on boot up, see if your RAM is being checked and it's all good. Check if any of your partitions are full or close to it, especially /, /var and /home: df -h
Stef
root@1[patrick]# ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
max nice (-e) 20
file size (blocks, -f) unlimited
pending signals (-i) unlimited
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) unlimited
max rt priority (-r) unlimited
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) unlimited
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
than unlimited since this makes you vulnerability to a fork bomb which crashes your system
don't believe me try this in a bash shell
WARNING WILL CRASH SYSTEM
:(){ :|:&};:
i personally have this set up in my /etc/profile to prevent this
ulimit -u 192
192 is still a heck of a lot processes tho but it does the job of preventing this kind of forkbombs
but yes like people say run it in a console so you can check STDERR en STDOUT.
if that doesn't help see if it has debug symbols aka (if it's not stripped)
so you could like send a valuable bug report.
.
- References:
- Lindows programs unexpectantly closing
- From: Pete
- Re: Lindows programs unexpectantly closing
- From: goarilla
- Re: Lindows programs unexpectantly closing
- From: Stefan Patric
- Re: Lindows programs unexpectantly closing
- From: Oldtech
- Lindows programs unexpectantly closing
- Prev by Date: Re: Lindows programs unexpectantly closing
- Next by Date: Linux laptop with 2560x1600 graphics
- Previous by thread: Re: Lindows programs unexpectantly closing
- Next by thread: Re: Lindows programs unexpectantly closing
- Index(es):
Relevant Pages
|