crashes tclsh while trying to upload a file

[GoogleCodeExporter]

What steps will reproduce the problem?
1. add Repo domain with upload 1
2. ensure you have no more than 51284 KiB of free RAM and no swap
3. upload any file of 5653856 bytes length

What is the expected output? What do you see instead?

Expected is that file is uploaded. Instead, Wub dies with this:
unable to alloc 11307732 bytes
Aborted

What version of the product are you using? On what operating system?
Revision: 2546

Please provide any additional information below.
evening_trk.gpx --- file to upload
core.18075 --- tclsh8.6 core dump
backtrace --- tclsh8.6 backtrace

Original issue reported on code.google.com by Andrew.Shadoura on 2 Jun 2010 at 9:47

Attachments:

• evening_trk.gpx
• core.18075

[GoogleCodeExporter]

http://shadoura.com/stuff/core.18075

Original comment by Andrew.Shadoura on 2 Jun 2010 at 9:51

Attachments:

• backtrace

[GoogleCodeExporter]

Issue 20 has been merged into this issue.

Original comment by mcc...@gmail.com on 2 Jun 2010 at 10:41

[GoogleCodeExporter]

This is an artefact of the way Wub handles request contents.  It loads them all 
into
RAM, even 'file upload' artefacts.

It's hard to know what to do about this, short of possibly determining that a 
given
content is either of file upload, or is very large, then dumping them to disk.

I'm open to suggestions.

Original comment by mcc...@gmail.com on 2 Jun 2010 at 10:43

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Current thinking is that the RAM available is too small to accept this size 
upload ... as strange as it seems, 10x overhead isn't unexpected.

Next thought - to save interactions over a certain size, then process them from 
disk may fail because tcllib's mime package may not (probably doesn't) process 
things without loading them from disk ... so we gain nothing in terms of RAM 
footprint.

Original comment by mcc...@gmail.com on 8 Jun 2010 at 8:11