Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <43847B42.6040904@slive.ca>
Date: Wed, 23 Nov 2005 09:22:58 -0500
From: Joshua Slive <joshua@slive.ca>
User-Agent: Thunderbird 1.4 (Windows/20050908)
MIME-Version: 1.0
To: Joshua Slive <joshua@slive.ca>,  dev@httpd.apache.org,
 infrastructure@apache.org
Subject: Re: 2.1.10-worker core dumps on minotaur
References: <438343CB.9080002@slive.ca> <43837A3D.5020401@force-elite.com>
 <43837B7C.4090200@slive.ca> <20051123110206.GD357@redhat.com>
In-Reply-To: <20051123110206.GD357@redhat.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit


Joe Orton wrote:
> On Tue, Nov 22, 2005 at 03:11:40PM -0500, Joshua Slive wrote:
>> Ahhh... Good idea.  I had just assumed based on the size of the dump 
>> that it had to be the threaded server.  But obviously svn requests are 
>> sometimes memory hungry as well.  I've appended the backtrace bellow 
>> (which is easy to get when you use the proper httpd), and yes it does 
>> seem to be in subversion.
>>
>>
>> #0  0x2840b777 in kill () from /lib/libc.so.5
>> #1  0x2840081e in raise () from /lib/libc.so.5
>> #2  0x2847415b in abort () from /lib/libc.so.5
>> #3  0x284f651c in abort_on_pool_failure (retcode=12)
>>     at ../../svn-current/subversion/libsvn_subr/pool.c:46
>> #4  0x28396bc4 in apr_palloc (pool=0x8120018, size=16)
> 
> Are all the debuggable crashes like this?  (The crash is due to malloc() 
> failing in case that's not clear)

At the time I sent it, that was the only non-truncated core.  We now 
have several more, and they all look about the same.  Interestingly, the 
core files are all almost exactly the same size (538 MB) which, along 
with the malloc failure, points strongly to hitting a resource limit 
someplace.  Any freebsd gurus want to comment?

Joshua.