Have you tried bisecting the config directives to see which is triggering
the memory abuse?
Sounds like the module might not be async-ready, but should httpd really be
doing many thread swaps before the listener thread is tripped?
Does one of your modules load a large table al la Geo IP mapping?
On 10/06/2017 10:26 AM, Bert Huijben wrote:
>
>
>> -Original Message-
>> From: Ruediger Pluem [mailto:rpl...@apache.org]
>> Sent: vrijdag 6 oktober 2017 09:47
>> To: Apache HTTP Server Development List
>> Subject: httpd memory consumption
>>
>> I am currently
On 10/06/2017 10:12 AM, Joe Orton wrote:
> On Fri, Oct 06, 2017 at 09:46:39AM +0200, Ruediger Pluem wrote:
>> For this I used the new dump_pool_and_children I added to .gdbinit which
>> delivers me the memory used by all
>> pools below 'apr_global_pool' and the amount of memory in the allocator
> -Original Message-
> From: Ruediger Pluem [mailto:rpl...@apache.org]
> Sent: vrijdag 6 oktober 2017 09:47
> To: Apache HTTP Server Development List
> Subject: httpd memory consumption
>
> I am currently looking at a core of a httpd 2.4 process using the event
On Fri, Oct 06, 2017 at 09:46:39AM +0200, Ruediger Pluem wrote:
> For this I used the new dump_pool_and_children I added to .gdbinit which
> delivers me the memory used by all
> pools below 'apr_global_pool' and the amount of memory in the allocator free
> lists associated to these pools.
> This
On 10/06/2017 09:56 AM, Stefan Eissing wrote:
> Were many threads spawned? Asking for a friend...
17 by httpd and 12 by the 3rd party module.
Additional information: no mod_http2 loaded :-)
Regards
RĂ¼diger
>
>> Am 06.10.2017 um 09:46 schrieb Ruediger Pluem :
>>
>> I am
Were many threads spawned? Asking for a friend...
> Am 06.10.2017 um 09:46 schrieb Ruediger Pluem :
>
> I am currently looking at a core of a httpd 2.4 process using the event MPM
> that consumed a lot of memory
> (core dump file size about 1.4 GB).
> While taking the core