public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Richard Fish <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] aterm do crash displaying long files, konsole don't: swappiness problem?
Date: Sun, 24 Jul 2005 12:24:19 +0200	[thread overview]
Message-ID: <42E36C53.1050304@asmallpond.org> (raw)
In-Reply-To: <20050724120942.0db9adfe.hilse@web.de>

Hans-Werner Hilse wrote:

>Hi,
>
>On Sun, 24 Jul 2005 10:52:06 +0200
>Fabrizio Prosperi <fprosper@interfree.it> wrote:
>
>  
>
>>Doing a long emerge -up world aterm kept crashing and I thought it was
>>an emerge problem, but then I focused on a particular emerge
>>(mozilla-firefox) and I realised it was it. 
>>
>>Just doing cat /var/log/portage/<that-log>.log
>>is making aterm crash again, but not konsole.
>>
>>I guess I something with swappiness settings, but how to fix it? 
>>    
>>
>
>Hm, don't know about aterm and its memory management, but that's for
>sure: _swappiness_ should have absolutely nothing to do with this. The
>swap management isn't up to userspace applications, that's kernel's
>matter. Well, there might be some small probability left that your swap
>management is somewhat hosed due to bugs in the kernel but that is very
>unlikely and wouldn't explain why these conditions only occur with
>aterm and only affect aterm.
>
>-hwh
>  
>

This may be a shot in the dark, since I don't use aterm, but can you 
check /var/log/messages and see if maybe the kernel is killing aterm due 
to excessive memory usage?  The search string is "oom" for "out-of-memory".

-Richard

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-07-24 10:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-24  8:52 [gentoo-user] aterm do crash displaying long files, konsole don't: swappiness problem? Fabrizio Prosperi
2005-07-24  9:23 ` Fabrizio Prosperi
2005-07-24 10:09 ` Hans-Werner Hilse
2005-07-24 10:24   ` Richard Fish [this message]
2005-07-24 11:33     ` Fabrizio Prosperi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42E36C53.1050304@asmallpond.org \
    --to=bigfish@asmallpond.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox