User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.95 Safari/537.36 Steps to reproduce: We allow large attachments (hundreds of megabytes) at Eclipse.org to support memory dumps. For years now when a bug with large attachments (total > 1G) is rendered in XML, the server's httpd process consumes all the server's available RAM until it swaps itself to death. We're running Bugzilla with mod_perl. I don't remember this ever happening when we were using CGI. Actual results: Here's what is seen from top while a bug with large attachments is being viewed as XML: 15703 (snip) 25 0 8781m 8.4g 3848 R 100 70.3 0:55.34 /home/local/data/httpd/b -f /etc/apache2/httpd.conf
The landfills have 1M attachment limits, and BMO has a 10M attachment limit, so I'm unable to confirm this anywhere else. In the meanwhile, I've reduced the max attachment to 100M on bugs.eclipse.org, but I can see some value in allowing large attachments.
You need to log in before you can comment on or make changes to this bug.