From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on archive.lwn.net X-Spam-Level: X-Spam-Status: No, score=-5.5 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by archive.lwn.net (Postfix) with ESMTP id 95EB57D90D for ; Sun, 27 Oct 2019 18:12:00 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727108AbfJ0SMA (ORCPT ); Sun, 27 Oct 2019 14:12:00 -0400 Received: from bombadil.infradead.org ([198.137.202.133]:35986 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727069AbfJ0SL7 (ORCPT ); Sun, 27 Oct 2019 14:11:59 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20170209; h=Content-Transfer-Encoding: Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:References:Cc:To:From: Subject:Sender:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=sH2Zby2rN0zJF2Tfh3LoyVFylZVEAMDvCcVAuNHhXV0=; b=azDziIydiDaEF1h+FpDISiw1W uMfN6rVX+Q444NFoPwGV+nW03rCAjMkWQurDEeybMe2M0EYXIw/0tZdr3uSsFnrkWqknDlQ12Pkj5 th9sEnk3F9iZlxuwXDMM/fTWbeOGEYTfghQoDhk+iMernWHi0g3yYQldpWhWP89O3CKiof80xwbLs GXhDJszwWfNdA6KkmddNUKnQASwwtqwOtktPeYfSDy/WWLxQDDYna4h8Cr6aODiQ1AORN74Z/5ymx LnREuyJx1a31u9r7Du7B4oDtu+bo1uzkcGbu4A5BS4KTRHPDhkw/KSUr/1ZEo1yGC53tNdHECRbPp amlPzrW2Q==; Received: from [2601:1c0:6280:3f0::9ef4] by bombadil.infradead.org with esmtpsa (Exim 4.92.3 #3 (Red Hat Linux)) id 1iOn1C-0006W3-Pw; Sun, 27 Oct 2019 18:11:58 +0000 Subject: Re: Sphinx parallel build errors From: Randy Dunlap To: Jonathan Corbet , Kees Cook Cc: "linux-doc@vger.kernel.org" , Mauro Carvalho Chehab References: <201910091929.0C058BB@keescook> <20191010124832.23bc4362@lwn.net> Message-ID: <8305ffe2-51ba-eb4b-4d44-2defe45aa68f@infradead.org> Date: Sun, 27 Oct 2019 11:11:57 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-doc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org On 10/10/19 1:15 PM, Randy Dunlap wrote: > On 10/10/19 11:48 AM, Jonathan Corbet wrote: >> On Wed, 9 Oct 2019 19:30:56 -0700 >> Kees Cook wrote: >> >>> I'm wondering if it's actually the addition of >>> the MAINTAINERS file parsing -- that's a really big parse and maybe that >>> pushed things over the edge? >> >> That does seem like a likely culprit, doesn't it? Watching a build here, >> though, I don't see that any one of the sphinx-build processes balloons to >> a horrific size, which is what I would expect if one file were causing the >> problem. >> >> In general, the sphinx build doesn't really begin to approach the memory >> requirements of, say, firefox or my mail client on my system. >> >> Randy, I'd be curious to know if you see the same behavior with current >> mainline. Also, can you see how many sphinx-build processes you have >> running? > > Yes, I see oom-kills when building docs for 5.4-rc2. > But only after I ran 'gimp *.jpg' for 22 photos. > > I can see anywhere from 1 to 4 sphinx-build processes running. I continue to have oom-kills when building docs. At least 2 times I also had system freezes where I had to power cycle to reboot. I suppose I can only hope that other people start running into this issue. :( -- ~Randy