From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sam Ravnborg Subject: Re: sparse triggers OOM killer Date: Tue, 17 Jan 2006 00:23:32 +0100 Message-ID: <20060116232332.GC8752@mars.ravnborg.org> References: <20060107111827.GA16133@mars.ravnborg.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from pasmtp.tele.dk ([193.162.159.95]:275 "EHLO pasmtp.tele.dk") by vger.kernel.org with ESMTP id S1751271AbWAPXXh (ORCPT ); Mon, 16 Jan 2006 18:23:37 -0500 Content-Disposition: inline In-Reply-To: Sender: linux-sparse-owner@vger.kernel.org List-Id: linux-sparse@vger.kernel.org To: Linus Torvalds Cc: linux-sparse@vger.kernel.org, linux-kernel@vger.kernel.org Hi Linus. On Sat, Jan 07, 2006 at 10:07:10AM -0800, Linus Torvalds wrote: > > > 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. Any news on this (call this a polite remineder)? I have not tried to dig into it myself - assuming that it will take me considerably time to do right.. Sam