Skip to content

App crashed on Heroku all the time #3260

New issue

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

Closed
deveristica opened this issue Dec 20, 2016 · 2 comments
Closed

App crashed on Heroku all the time #3260

deveristica opened this issue Dec 20, 2016 · 2 comments

Comments

@deveristica
Copy link

After updating to the version 2.3.1 my app started crashing on heroku all the time.

Environment Setup

  • Server

    • parse-server version (Be specific! Don't say 'latest'.) : 2.3.1
    • Operating System: Linux
    • Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): Heroku
  • Database

    • MongoDB version: 3.0.11
    • Localhost or remote server? (AWS, mLab, ObjectRocket, Digital Ocean, etc): mlab

Logs/Trace

2016-12-20T10:07:23.529039+00:00 app[web.1]:
2016-12-20T10:07:23.529050+00:00 app[web.1]: <--- Last few GCs --->
2016-12-20T10:07:23.529050+00:00 app[web.1]:
2016-12-20T10:07:23.529051+00:00 app[web.1]: 144559 ms: Mark-sweep 1310.5 (1436.4) -> 1310.5 (1436.4) MB, 841.9 / 0.0 ms [allocation failure] [GC in old space requested].
2016-12-20T10:07:23.529052+00:00 app[web.1]: 145395 ms: Mark-sweep 1310.5 (1436.4) -> 1310.4 (1436.4) MB, 835.6 / 0.0 ms [allocation failure] [GC in old space requested].
2016-12-20T10:07:23.529053+00:00 app[web.1]: 146236 ms: Mark-sweep 1310.4 (1436.4) -> 1314.0 (1414.4) MB, 840.4 / 0.0 ms [last resort gc].
2016-12-20T10:07:23.529054+00:00 app[web.1]: 147075 ms: Mark-sweep 1314.0 (1414.4) -> 1317.7 (1414.4) MB, 839.3 / 0.0 ms [last resort gc].
2016-12-20T10:07:23.529054+00:00 app[web.1]:
2016-12-20T10:07:23.529055+00:00 app[web.1]:
2016-12-20T10:07:23.529055+00:00 app[web.1]: <--- JS stacktrace --->
2016-12-20T10:07:23.529056+00:00 app[web.1]:
2016-12-20T10:07:23.529057+00:00 app[web.1]: ==== JS stack trace =========================================
2016-12-20T10:07:23.529057+00:00 app[web.1]:
2016-12-20T10:07:23.529058+00:00 app[web.1]: Security context: 0x1af7399cfb51
2016-12-20T10:07:23.529060+00:00 app[web.1]: 1: deserializeObject(aka deserializeObject) [/app/node_modules/bson/lib/bson/parser/deserializer.js:~39] [pc=0x213c813091e4] (this=0x1af739904381 ,buffer=0x1443d3fe33e1 <an Uint8Array with map 0x2e89d5006829>,index=0,options=0x1443d3fe33b1 <an Object with map 0x362ac767dd59>,isArray=0x1af739904381 )
2016-12-20T10:07:23.529060+00:00 app[web.1]: 2: deserialize(aka deserialize) [/app/node_modules/bson/lib/bson/p...
2016-12-20T10:07:23.529061+00:00 app[web.1]:
2016-12-20T10:07:23.529062+00:00 app[web.1]: FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
2016-12-20T10:07:23.532267+00:00 app[web.1]: 1: node::Abort() [node]
2016-12-20T10:07:23.532787+00:00 app[web.1]: 2: 0x1098b2c [node]
2016-12-20T10:07:23.533211+00:00 app[web.1]: 3: v8::Utils::ReportApiFailure(char const*, char const*) [node]
2016-12-20T10:07:23.533625+00:00 app[web.1]: 4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [node]
2016-12-20T10:07:23.534156+00:00 app[web.1]: 5: v8::internal::Factory::NewTransitionArray(int) [node]
2016-12-20T10:07:23.534704+00:00 app[web.1]: 6: v8::internal::TransitionArray::Insert(v8::internal::Handlev8::internal::Map, v8::internal::Handlev8::internal::Name, v8::internal::Handlev8::internal::Map, v8::internal::SimpleTransitionFlag) [node]
2016-12-20T10:07:23.535265+00:00 app[web.1]: 7: v8::internal::Map::CopyReplaceDescriptors(v8::internal::Handlev8::internal::Map, v8::internal::Handlev8::internal::DescriptorArray, v8::internal::Handlev8::internal::LayoutDescriptor, v8::internal::TransitionFlag, v8::internal::MaybeHandlev8::internal::Name, char const*, v8::internal::SimpleTransitionFlag) [node]
2016-12-20T10:07:23.535825+00:00 app[web.1]: 8: v8::internal::Map::CopyAddDescriptor(v8::internal::Handlev8::internal::Map, v8::internal::Descriptor*, v8::internal::TransitionFlag) [node]
2016-12-20T10:07:23.536396+00:00 app[web.1]: 9: v8::internal::Map::CopyWithField(v8::internal::Handlev8::internal::Map, v8::internal::Handlev8::internal::Name, v8::internal::Handlev8::internal::FieldType, v8::internal::PropertyAttributes, v8::internal::Representation, v8::internal::TransitionFlag) [node]
2016-12-20T10:07:23.536954+00:00 app[web.1]: 10: v8::internal::Map::TransitionToDataProperty(v8::internal::Handlev8::internal::Map, v8::internal::Handlev8::internal::Name, v8::internal::Handlev8::internal::Object, v8::internal::PropertyAttributes, v8::internal::Object::StoreFromKeyed) [node]
2016-12-20T10:07:23.537509+00:00 app[web.1]: 11: v8::internal::LookupIterator::PrepareTransitionToDataProperty(v8::internal::Handlev8::internal::JSObject, v8::internal::Handlev8::internal::Object, v8::internal::PropertyAttributes, v8::internal::Object::StoreFromKeyed) [node]
2016-12-20T10:07:23.538063+00:00 app[web.1]: 12: v8::internal::Object::AddDataProperty(v8::internal::LookupIterator*, v8::internal::Handlev8::internal::Object, v8::internal::PropertyAttributes, v8::internal::Object::ShouldThrow, v8::internal::Object::StoreFromKeyed) [node]
2016-12-20T10:07:23.538609+00:00 app[web.1]: 13: v8::internal::Object::SetProperty(v8::internal::LookupIterator*, v8::internal::Handlev8::internal::Object, v8::internal::LanguageMode, v8::internal::Object::StoreFromKeyed) [node]
2016-12-20T10:07:23.539157+00:00 app[web.1]: 14: v8::internal::Runtime::SetObjectProperty(v8::internal::Isolate*, v8::internal::Handlev8::internal::Object, v8::internal::Handlev8::internal::Object, v8::internal::Handlev8::internal::Object, v8::internal::LanguageMode) [node]
2016-12-20T10:07:23.539706+00:00 app[web.1]: 15: v8::internal::Runtime_SetProperty(int, v8::internal::Object**, v8::internal::Isolate*) [node]
2016-12-20T10:07:23.539709+00:00 app[web.1]: 16: 0x213c7f2092a7
2016-12-20T10:07:23.631119+00:00 app[web.1]: Aborted
2016-12-20T10:07:23.636387+00:00 app[web.1]:
2016-12-20T10:07:23.644317+00:00 app[web.1]: npm ERR! Linux 3.13.0-105-generic
2016-12-20T10:07:23.644571+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
2016-12-20T10:07:23.644910+00:00 app[web.1]: npm ERR! node v6.9.1
2016-12-20T10:07:23.645090+00:00 app[web.1]: npm ERR! npm v3.10.8
2016-12-20T10:07:23.645271+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2016-12-20T10:07:23.645419+00:00 app[web.1]: npm ERR! [email protected] start: node index.js
2016-12-20T10:07:23.645544+00:00 app[web.1]: npm ERR! Exit status 134
2016-12-20T10:07:23.645684+00:00 app[web.1]: npm ERR!
2016-12-20T10:07:23.645806+00:00 app[web.1]: npm ERR! Failed at the [email protected] start script 'node index.js'.
2016-12-20T10:07:23.645930+00:00 app[web.1]: npm ERR! Make sure you have the latest version of node.js and npm installed.
2016-12-20T10:07:23.646055+00:00 app[web.1]: npm ERR! If you do, this is most likely a problem with the parse-server-example package,
2016-12-20T10:07:23.646181+00:00 app[web.1]: npm ERR! not with npm itself.
2016-12-20T10:07:23.646319+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system:
2016-12-20T10:07:23.646446+00:00 app[web.1]: npm ERR! node index.js
2016-12-20T10:07:23.646575+00:00 app[web.1]: npm ERR! You can get information on how to open an issue for this project with:
2016-12-20T10:07:23.646704+00:00 app[web.1]: npm ERR! npm bugs parse-server-example
2016-12-20T10:07:23.646829+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via:
2016-12-20T10:07:23.646958+00:00 app[web.1]: npm ERR! npm owner ls parse-server-example
2016-12-20T10:07:23.647083+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
2016-12-20T10:07:23.664036+00:00 app[web.1]:
2016-12-20T10:07:23.664245+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2016-12-20T10:07:23.664461+00:00 app[web.1]: npm ERR! /app/npm-debug.log

@deveristica
Copy link
Author

So after the last update I get this error quite a lot. When I send a push to every user, when I query for some objects.

@hramos
Copy link
Contributor

hramos commented Feb 10, 2017

Debugging why a particular app crashes may be out of scope for a GitHub issue. If you can drill this down to something specific in Parse Server, can you open a new issue then?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants