Memory leak?
Closed this issue · 1 comments
addreas commented
2018-11-03T08:05:00.138060057Z app[web.1]: fetching https://calypso.datasektionen.se/api/item/7083
2018-11-03T08:05:08.836147776Z app[web.1]: fetching https://taitan.datasektionen.se/en/clubs/informationsorganet
2018-11-03T08:05:39.524897356Z app[web.1]: fetching https://taitan.datasektionen.se/kalender.ics/
2018-11-03T08:05:41.811316103Z app[web.1]: fetching https://taitan.datasektionen.se/kalender.ics/
2018-11-03T08:06:02.420559251Z app[web.1]: fetching https://calypso.datasektionen.se/api/item/7083
2018-11-03T08:06:42.571090640Z app[web.1]: FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
2018-11-03T08:06:42.571111079Z app[web.1]:
2018-11-03T08:06:42.571146964Z app[web.1]: <--- Last few GCs --->
2018-11-03T08:06:42.571152175Z app[web.1]:
2018-11-03T08:06:42.571155764Z app[web.1]: [194:0x25ceea0] 560136016 ms: Mark-sweep 1303.2 (1455.1) -> 1303.2 (1455.1) MB, 2244.0 / 0.0 ms (average mu = 0.179, current mu = 0.006) last resort GC in old space requested
2018-11-03T08:06:42.571159872Z app[web.1]: [194:0x25ceea0] 560138350 ms: Mark-sweep 1303.2 (1455.1) -> 1303.2 (1455.1) MB, 2333.2 / 0.0 ms (average mu = 0.097, current mu = 0.000) last resort GC in old space requested
2018-11-03T08:06:42.571163879Z app[web.1]:
2018-11-03T08:06:42.571167187Z app[web.1]:
2018-11-03T08:06:42.571170585Z app[web.1]: <--- JS stacktrace --->
2018-11-03T08:06:42.571174162Z app[web.1]:
2018-11-03T08:06:42.571177524Z app[web.1]: ==== JS stack trace =========================================
2018-11-03T08:06:42.571181047Z app[web.1]:
2018-11-03T08:06:42.571184330Z app[web.1]: 0: ExitFrame [pc: 0x22d34515be1d]
2018-11-03T08:06:42.571187763Z app[web.1]: 1: StubFrame [pc: 0x22d345185af3]
2018-11-03T08:06:42.571191185Z app[web.1]: Security context: 0x0caa2511e6e1 <JSObject>
2018-11-03T08:06:42.571194775Z app[web.1]: 2: send [0x2e605b5bdd69] [/app/node_modules/express/lib/response.js:221] [bytecode=0x317e0dee6221 offset=688](this=0x068c2da45159 <ServerResponse map = 0x40ed9f7b361>,body=0x06a0d609b3c1 <Very long string[18880]>)
2018-11-03T08:06:42.571199068Z app[web.1]: 3: /* anonymous */(aka /* anonymous */) [0x68c2da468f1] [/app/build/server.js:1] [bytecode=0x267f919...
2018-11-03T08:06:42.571202673Z app[web.1]:
2018-11-03T08:06:42.596874034Z app[web.1]: 1: 0x8daaa0 node::Abort() [node]
2018-11-03T08:06:42.597227645Z app[web.1]: 2: 0x8daaec [node]
2018-11-03T08:06:42.599720868Z app[web.1]: 3: 0xad79ae v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
2018-11-03T08:06:42.601597269Z app[web.1]: 4: 0xad7be4 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
2018-11-03T08:06:42.602335080Z app[web.1]: 5: 0xece9e2 [node]
2018-11-03T08:06:42.604394826Z app[web.1]: 6: 0xede2df v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [node]
2018-11-03T08:06:42.605077996Z app[web.1]: 7: 0xea6356 [node]
2018-11-03T08:06:42.605794880Z app[web.1]: 8: 0xeb8c37 v8::internal::Factory::NewLoadHandler(int) [node]
2018-11-03T08:06:42.607820542Z app[web.1]: 9: 0xf3835b v8::internal::LoadHandler::LoadFromPrototype(v8::internal::Isolate*, v8::internal::Handle<v8::internal::Map>, v8::internal::Handle<v8::internal::JSReceiver>, v8::internal::Handle<v8::internal::Smi>, v8::internal::MaybeHandle<v8::internal::Object>, v8::internal::MaybeHandle<v8::internal::Object>) [node]
2018-11-03T08:06:42.609058748Z app[web.1]: 10: 0xf3fd2f v8::internal::LoadIC::ComputeHandler(v8::internal::LookupIterator*) [node]
2018-11-03T08:06:42.610239545Z app[web.1]: 11: 0xf46bec v8::internal::LoadIC::UpdateCaches(v8::internal::LookupIterator*) [node]
2018-11-03T08:06:42.612644805Z app[web.1]: 12: 0xf4732c v8::internal::LoadIC::Load(v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Name>) [node]
2018-11-03T08:06:42.615040208Z app[web.1]: 13: 0xf4be32 v8::internal::Runtime_LoadIC_Miss(int, v8::internal::Object**, v8::internal::Isolate*) [node]
2018-11-03T08:06:42.615054876Z app[web.1]: 14: 0x22d34515be1d
2018-11-03T08:06:43.110924272Z app[web.1]: Aborted (core dumped)
2018-11-03T08:06:43.546815832Z app[web.1]: npm ERR! code ELIFECYCLE
2018-11-03T08:06:43.554624473Z app[web.1]: npm ERR! errno 134
2018-11-03T08:06:43.596047990Z app[web.1]: npm ERR! bawang@ start: `node -r esm build/server.js`
2018-11-03T08:06:43.596580096Z app[web.1]: npm ERR! Exit status 134
2018-11-03T08:06:43.597304925Z app[web.1]: npm ERR!
2018-11-03T08:06:43.597316239Z app[web.1]: npm ERR! Failed at the bawang@ start script.
2018-11-03T08:06:43.597355125Z app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2018-11-03T08:06:43.718201750Z app[web.1]:
2018-11-03T08:06:43.720084101Z app[web.1]: npm ERR! A complete log of this run can be found in:
2018-11-03T08:06:43.720100673Z app[web.1]: npm ERR! /app/.npm/_logs/2018-11-03T08_06_43_657Z-debug.log
2018-11-03T08:06:48.132907878Z app[web.1]: Could not determine a reasonable value for WEB_CONCURRENCY.
2018-11-03T08:06:48.132941769Z app[web.1]: This is likely due to running the Heroku NodeJS buildpack on a non-Heroku
2018-11-03T08:06:48.132946351Z app[web.1]: platform.
2018-11-03T08:06:48.132949761Z app[web.1]:
2018-11-03T08:06:48.132953026Z app[web.1]: WEB_CONCURRENCY has been set to 1. Please review whether this value is
2018-11-03T08:06:48.132956656Z app[web.1]: appropriate for your application.
2018-11-03T08:06:48.132960042Z app[web.1]:
2018-11-03T08:06:48.653927726Z app[web.1]:
2018-11-03T08:06:48.653962348Z app[web.1]: > bawang@ start /app
2018-11-03T08:06:48.653967154Z app[web.1]: > node -r esm build/server.js
2018-11-03T08:06:48.653970740Z app[web.1]:
2018-11-03T08:06:52.395967874Z app[web.1]: 🚀 started on port 5000
DokID commented
As far as I know this hasn't occurred since, so I am closing the issue.