From: Linus Torvalds <torvalds@osdl.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-sparse@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: sparse triggers OOM killer
Date: Sat, 7 Jan 2006 10:07:10 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0601071004130.3169@g5.osdl.org> (raw)
In-Reply-To: <20060107111827.GA16133@mars.ravnborg.org>
On Sat, 7 Jan 2006, Sam Ravnborg wrote:
>
> There was no oops or similar and sparse just exited after a while with
> an errorcode (137).
That's just SIGKILL (128+9). Which is normal for the OOM killer.
> Now I wonder if I have hit a bug in sparse or this is what I should
> expect.
Well, sparse does keep a _lot_ of stuff in memory, and the "do many files
at once" will basically keep every single one (with full types, full
linearization etc) in memory at the same time.
It's probably fairly easy to fix: I should just make sparse release all
the linearizations and symbols when they go out of file scope.
The "do many files at once" thing really was just a quick hack, so the
lack of memory release is not that susprising.
I'll see what I can do.
Linus
next prev parent reply other threads:[~2006-01-07 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 11:18 Sam Ravnborg
2006-01-07 18:07 ` Linus Torvalds [this message]
2006-01-16 23:23 ` Sam Ravnborg
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=Pine.LNX.4.64.0601071004130.3169@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=sam@ravnborg.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
all inboxes | Powered by JetHome®