Doesn't support large files

[elliot-sawyer]

Tried to upload a 50MB assets.tar.gz file to a company paste server and got a heap limit failure.

Not expecting a fix, but might be good to document it as a known limitation

pastey assets.tar.gz 

<--- Last few GCs --->

[210583:0x5b65270]    67546 ms: Scavenge 4050.0 (4118.1) -> 4049.8 (4128.9) MB, 19.7 / 0.0 ms  (average mu = 0.202, current mu = 0.136) allocation failure; 
[210583:0x5b65270]    67574 ms: Scavenge 4056.8 (4128.9) -> 4057.5 (4129.6) MB, 21.6 / 0.0 ms  (average mu = 0.202, current mu = 0.136) allocation failure; 
[210583:0x5b65270]    69744 ms: Scavenge 4057.6 (4129.6) -> 4056.7 (4152.9) MB, 2169.3 / 0.0 ms  (average mu = 0.202, current mu = 0.136) allocation failure; 


<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
 1: 0xb7a940 node::Abort() [pastey]
 2: 0xa8e823  [pastey]
 3: 0xd5c940 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [pastey]
 4: 0xd5cce7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [pastey]
 5: 0xf3a3e5  [pastey]
 6: 0xf4c8cd v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [pastey]
 7: 0xf26fce v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [pastey]
 8: 0xf28397 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [pastey]
 9: 0xf0956a v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [pastey]
10: 0x12ce7af v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [pastey]
11: 0x16fb6b9  [pastey]
[1]    210583 abort (core dumped)  pastey assets.tar.gz

[xurizaemon]

Looks like fincham/paste will reject pastes over 10MB. I didn't know that either.

This error looks like it's in the client, though. This might be dependent on available resources (and yes, I know you got moar RAM recently lol). Thanks, appreciate knowing this can happen!

I wonder what the behaviour is for uploads of .tar.gz type assets, ie not plain text and not an image. I suspect but haven't checked that uploading an image may do a data encode before upload, and then upload it as a string containing the image.

I don't know how the same service would handle uploads of non-image assets, and am interested if you've tried the web UI with a small test .tgz?