Received: (qmail 60841 invoked by uid 501); 21 Feb 2002 13:13:35 -0000
Message-Id: <20020221131335.60840.qmail@apache.org>
Date: 21 Feb 2002 13:13:35 -0000
From: annichilez <annichilez@hotmail.com>
Reply-To: annichilez@hotmail.com
To: submit@bugz.apache.org
Subject: Crash if the output size is too large.
X-Send-Pr-Version: 3.110

>Number:         9898
>Category:       os-windows
>Synopsis:       Crash if the output size is too large.
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    apache
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Feb 21 05:20:00 PST 2002
>Closed-Date:    Thu Feb 21 21:47:23 PST 2002
>Last-Modified:  Thu Feb 21 21:47:23 PST 2002
>Originator:     annichilez@hotmail.com
>Release:        2.0.32
>Organization:
>Environment:
2.0.32 binary from apache.org
mod_ssl.so compile by Visual C++ 6.0 sp4 in Windows 2000 english version
with open_SSL 0.9.6c
Run in Windows XP english version
>Description:
If the ouput content size is too large, the Apache will crash, both the child process and parent process.

For example, if I try to download a 5MB file.
The apache will try to output something, but the browser can only get 32KB/64KB.
And then the Apache itself crash.
>How-To-Repeat:
I can always repeat it easily.
The same problem seem exist in 2.0.28. But the maximium usable content size is bigger in 2.0.28. But in 2.0.28, the crash point seems change case by case.
But in 2.0.32, the crash point seems always be 32KB and 64KB.
>Fix:

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open-closed
State-Changed-By: wrowe
State-Changed-When: Thu Feb 21 21:47:23 PST 2002
State-Changed-Why:
This was a bug in the apr mmap implementation for Win32,
and has been corrected.  The fix is available for building
from nightly snapshots or the current cvs.

Thanks for your report and trying the Apache 2.0.32 beta!
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]