[Bug 60353] New: Uploading a large file causes mod_fcgid to overuse memory and eventually crash

[b***@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=60353

Bug ID: 60353
Summary: Uploading a large file causes mod_fcgid to overuse
memory and eventually crash
Product: Apache httpd-2
Version: 2.5-HEAD
Hardware: PC
Status: NEW
Severity: normal
Priority: P2
Component: mod_fcgid
Assignee: ***@httpd.apache.org
Reporter: ***@gmail.com
Target Milestone: ---

Created attachment 34428
--> https://bz.apache.org/bugzilla/attachment.cgi?id=34428&action=edit
upload script

Hi,

When i'm uploading a large file (~270 MB) using the attached script
(upload.php), mod_fcgid tries to send it to the PHP process and causes a crash
in httpd.exe.
The proc_write_ipc function gets the apr_bucket_brigade list and sends the
buckets one by one to the PHP process and is using a lot of memory until a
point where 'malloc' returns NULL (through allocator_alloc ) and httpd
immediately crashes.

I've attached a suggestion for a patch to this function where the httpd is
using significantly less memory and the crash is gone. It basically frees each
apr_bucket after it is sent to the php process.

thanks!

[b***@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=60353

--- Comment #1 from Oz Gilat <***@gmail.com> ---
Created attachment 34429
--> https://bz.apache.org/bugzilla/attachment.cgi?id=34429&action=edit
proposed patch

[b***@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=60353

Oz Gilat <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Attachment #34429|0 |1
is patch| |
Attachment #34429|application/octet-stream |text/plain
mime type| |

[b***@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=60353

Joe Orton <***@redhat.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Status|NEW |RESOLVED

--- Comment #2 from Joe Orton <***@redhat.com> ---


*** This bug has been marked as a duplicate of bug 51747 ***