We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A month ago I was able to deploy it without any issues.
Using:
{ "devDependencies": { "serverless": "^3.27.0", "serverless-plugin-warmup": "^8.2.1", "serverless-prune-plugin": "^2.0.2" } }
sls deploy -s dev-live --verbose ... Excluding development dependencies for function "warmUpPluginDefault" ⠦ Packaging (1s) <--- Last few GCs ---> [1416384:0x2f8f4b0] 361600 ms: Mark-sweep 4049.8 (4131.1) -> 4034.1 (4131.3) MB, 1221.0 / 0.0 ms (average mu = 0.153, current mu = 0.045) allocation failure scavenge might not succeed [1416384:0x2f8f4b0] 364426 ms: Mark-sweep 4050.2 (4131.3) -> 4035.2 (4132.3) MB, 2770.8 / 0.0 ms (average mu = 0.079, current mu = 0.019) allocation failure scavenge might not succeed <--- JS stacktrace ---> FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory 1: 0x99e1e0 node::Abort() [sls] 2: 0x8c9613 node::FatalError(char const*, char const*) [sls] 3: 0x1069a0e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [sls] 4: 0x1069cb6 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [sls] 5: 0x1229e35 [sls] 6: 0x122ab6e v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [sls] 7: 0x1238ded v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [sls] 8: 0x123975a v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [sls] 9: 0x123ca0b v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [sls] 10: 0x11f9685 v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [sls] 11: 0x11f1df4 v8::internal::FactoryBase<v8::internal::Factory>::AllocateRawWithImmortalMap(int, v8::internal::AllocationType, v8::internal::Map, v8::internal::AllocationAlignment) [sls] 12: 0x11f3b5f v8::internal::FactoryBase<v8::internal::Factory>::NewRawOneByteString(int, v8::internal::AllocationType) [sls] 13: 0x149e6ba v8::internal::String::SlowFlatten(v8::internal::Isolate*, v8::internal::Handle<v8::internal::ConsString>, v8::internal::AllocationType) [sls] 14: 0x15bc696 v8::internal::Runtime_StringCharCodeAt(int, unsigned long*, v8::internal::Isolate*) [sls] 15: 0x198cdb9 [sls] [1] 1416384 abort (core dumped) sls deploy -s dev-live --verbose
If I comment out lines:
warmup: default: enabled: # - dev-live # - prod-live
Deployments go without a hitch.
The text was updated successfully, but these errors were encountered:
I've checked out the repo in a new folder and all seem to have worked. Trying to find out what's wrong with my original working folder.
Sorry, something went wrong.
Hmmm strange...
I can't think of any reason for a serverless deployment to exhaust Node's memory.
I'll close this since it seems resolved now.
No branches or pull requests
A month ago I was able to deploy it without any issues.
Using:
If I comment out lines:
Deployments go without a hitch.
The text was updated successfully, but these errors were encountered: