Security context: 0x99ecc5e3ac1 Error

[zhangxiao918]

Please read the following instructions carefully.

Check out #1271 for an ideal bug report.
The closer your issue report is to that one, the more likely we are to be able to help, and the more likely we will be to fix the issue quickly!

Many members of the community use Stack Overflow and Server Fault to ask questions.
Read through the existing questions or ask your own!

• Stack Overflow: http://stackoverflow.com/questions/tagged/parse.com
• Server Fault: https://serverfault.com/tags/parse

For database migration help, please file a bug report at https://parse.com/help#report

Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!

• You've met the prerequisites: https://github.com/ParsePlatform/parse-server/wiki/Parse-Server-Guide#prerequisites.

• You're running the latest version of Parse Server: https://github.com/ParsePlatform/parse-server/releases

• You've searched through existing issues: https://github.com/ParsePlatform/Parse-Server/issues?utf8=%E2%9C%93&q=is%3Aissue Chances are that your issue has been reported or resolved before.

• You have filled out every section below. Issues without sufficient information are more likely to be closed.

--

Issue Description

[DELETE EVERYTHING ABOVE THIS LINE BEFORE SUBMITTING YOUR ISSUE]

Describe your issue in as much detail as possible.

[FILL THIS OUT]

Steps to reproduce

Please include a detailed list of steps that reproduce the issue. Include curl commands when applicable.

1. SEND 100k install to Parse-Server
2. [FILL THIS OUT]
3. [FILL THIS OUT]

Expected Results

100k push success

Actual Outcome

[FILL THIS OUT]

Environment Setup

• Server

  • parse-server version (Be specific! Don't say 'latest'.) :2.2.23
  • Operating System: Linux
  • Hardware: HEROKU
  • Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): [FILL THIS OUT]

• Database

  • MongoDB version: 3.0.9
  • Storage engine: MMAPv1
  • Hardware: ObjectRocket
  • Localhost or remote server? (AWS, mLab, ObjectRocket, Digital Ocean, etc):REMOTE SERVER

Logs/Trace

You can turn on additional logging by configuring VERBOSE=1 in your environment.

2016-11-01T02:42:16.163695+00:00 app[web.1]: FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory
2016-11-01T02:42:16.163706+00:00 app[web.1]:
2016-11-01T02:42:16.163708+00:00 app[web.1]: <--- Last few GCs --->
2016-11-01T02:42:16.163709+00:00 app[web.1]:
2016-11-01T02:42:16.163710+00:00 app[web.1]: 1347889 ms: Scavenge 1398.6 (1458.0) -> 1398.6 (1458.0) MB, 0.6 / 0 ms (+ 1.0 ms in 1 steps since last GC) [allocation failure] [incremental marking delaying mark-sweep].
2016-11-01T02:42:16.163711+00:00 app[web.1]: 1349796 ms: Mark-sweep 1398.6 (1458.0) -> 1390.6 (1458.0) MB, 1907.9 / 0 ms (+ 1.0 ms in 1 steps since start of marking, biggest step 1.0 ms) [last resort gc].
2016-11-01T02:42:16.163713+00:00 app[web.1]: 1351696 ms: Mark-sweep 1390.6 (1458.0) -> 1392.8 (1458.0) MB, 1899.9 / 0 ms [last resort gc].
2016-11-01T02:42:16.163713+00:00 app[web.1]:
2016-11-01T02:42:16.163713+00:00 app[web.1]:
2016-11-01T02:42:16.163714+00:00 app[web.1]: <--- JS stacktrace --->
2016-11-01T02:42:16.163715+00:00 app[web.1]:
2016-11-01T02:42:16.163716+00:00 app[web.1]: ==== JS stack trace =========================================
2016-11-01T02:42:16.163717+00:00 app[web.1]:
2016-11-01T02:42:16.163718+00:00 app[web.1]: Security context: 0x99ecc5e3ac1
2016-11-01T02:42:16.163719+00:00 app[web.1]: 1: /* anonymous /(aka / anonymous */) [/app/node_modules/parse-server/lib/Adapters/Storage/Mongo/MongoTransform.js:902] [pc=0x14fb5b3437ae] (this=0x99ecc504189 )
2016-11-01T02:42:16.282175+00:00 heroku[router]: at=error code=H13 desc="Connection closed without response" method=POST path="/parse/classes/_Installation" host=push.wanews.co request_id=2c9f5959-c612-4195-811f-b2eb2675a810 fwd="115.82.20.39" dyno=web.1 connect=2ms service=27097ms status=503 bytes=0
2016-11-01T02:42:16.163721+00:00 app[web.1]: 2: mongoObjectToParseObject(aka mongoObjectToParseObject) [/app/node_modules/parse-server/lib/Adapters/Storage/Mongo/MongoTransform.js:~734] [pc=0x14fb5b36838e] (this=0x99ecc504189 ,className=0x1922ea96de...
2016-11-01T02:42:16.163721+00:00 app[web.1]:
2016-11-01T02:42:16.264268+00:00 app[web.1]: Aborted
2016-11-01T02:42:16.269038+00:00 app[web.1]:
2016-11-01T02:42:16.275758+00:00 app[web.1]: npm ERR! Linux 3.13.0-100-generic
2016-11-01T02:42:16.282380+00:00 heroku[router]: at=error code=H13 desc="Connection closed without response" method=POST path="/parse/classes/_Installation" host=push.wanews.co request_id=cb3c32de-3eab-4848-bbbb-8d77b5616e7e fwd="114.136.9.32" dyno=web.1 connect=1ms service=18930ms status=503 bytes=0
2016-11-01T02:42:16.276096+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
2016-11-01T02:42:16.276305+00:00 app[web.1]: npm ERR! node v5.11.1
2016-11-01T02:42:16.277162+00:00 app[web.1]: npm ERR! npm v3.8.6
2016-11-01T02:42:16.277362+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2016-11-01T02:42:16.277519+00:00 app[web.1]: npm ERR! parse-server-example@1.4.0 start: node index.js
2016-11-01T02:42:16.277662+00:00 app[web.1]: npm ERR! Exit status 134
2016-11-01T02:42:16.277820+00:00 app[web.1]: npm ERR!
2016-11-01T02:42:16.277969+00:00 app[web.1]: npm ERR! Failed at the parse-server-example@1.4.0 start script 'node index.js'.
2016-11-01T02:42:16.282563+00:00 heroku[router]: at=error code=H13 desc="Connection closed without response" method=POST path="/parse/classes/_Installation" host=push.wanews.co request_id=e17ad2b7-65d9-4784-9a80-33bbaf93fd98 fwd="115.27.201.230" dyno=web.1 connect=1ms service=12883ms status=503 bytes=0
2016-11-01T02:42:16.278123+00:00 app[web.1]: npm ERR! Make sure you have the latest version of node.js and npm installed.
2016-11-01T02:42:16.278267+00:00 app[web.1]: npm ERR! If you do, this is most likely a problem with the parse-server-example package,
2016-11-01T02:42:16.278410+00:00 app[web.1]: npm ERR! not with npm itself.
2016-11-01T02:42:16.278549+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system:
2016-11-01T02:42:16.278700+00:00 app[web.1]: npm ERR! node index.js
2016-11-01T02:42:16.278840+00:00 app[web.1]: npm ERR! You can get information on how to open an issue for this project with:
2016-11-01T02:42:16.278984+00:00 app[web.1]: npm ERR! npm bugs parse-server-example
2016-11-01T02:42:16.279123+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via:
2016-11-01T02:42:16.279267+00:00 app[web.1]: npm ERR! npm owner ls parse-server-example
2016-11-01T02:42:16.279437+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
2016-11-01T02:42:16.282427+00:00 app[web.1]:
2016-11-01T02:42:16.282624+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2016-11-01T02:42:16.282757+00:00 app[web.1]: npm ERR! /app/npm-debug.log

[bohemima]

You're running out of memory. "Allocation failed - process out of memory". What did you do when it happened?

[flovilmart]

Sent 100k push. Which obviously either would take a lot of memory with the current architecture

[zhangxiao918]

@bohemima when we push topic message to our use who subscirbe boardcast channel , we have almost 400k installations in _Installation Collection and most of these installation have deviceToken .
so when we push some message with boardcast channel , this problem happend. we don't know how to fix this bug. and we haven't any node developer . MD.MD.

[zhangxiao918]

@flovilmart we don't know how to fix this bug. can you help us ?

[flovilmart]

I don't know how to fix this bug either.

[zhangxiao918]

@flovilmart is there any loop send push for huge installations for one broadcast channel push request?

[zhangxiao918]

MD,MD!

[cipiripper]

I had a similar issue. Parse-server used up all disk space when logging stuff to ./logs/ (even though VERBOSE is false). This is really a bad thing... which went unnoticed on my server because it had a lot of HDD space.

Quick fix is to rm -rf /parse-server/logs.

(just commenting for someone like me who googled to here...)

parse-server-0 (out): <--- Last few GCs --->
parse-server-0 (out): 
parse-server-0 (out):   687957 ms: Mark-sweep 1363.8 (1439.5) -> 1363.7 (1439.5) MB, 215.5 / 0 ms [allocation failure] [GC in old space requested].
parse-server-0 (out):   688164 ms: Mark-sweep 1363.7 (1439.5) -> 1363.7 (1439.5) MB, 207.0 / 0 ms [allocation failure] [GC in old space requested].
parse-server-0 (out):   688379 ms: Mark-sweep 1363.7 (1439.5) -> 1361.8 (1439.5) MB, 214.4 / 0 ms [last resort gc].
parse-server-0 (out):   688585 ms: Mark-sweep 1361.8 (1439.5) -> 1342.6 (1439.5) MB, 206.1 / 0 ms [last resort gc].
parse-server-0 (out): 
parse-server-0 (out): 
parse-server-0 (out): <--- JS stacktrace --->
parse-server-0 (out): 
parse-server-0 (out): ==== JS stack trace =========================================
parse-server-0 (out): 
parse-server-0 (out): Security context: 0x1d478a737399 <JS Object>
parse-server-0 (out):     2: /* anonymous */(aka /* anonymous */) [/home/parse/node_modules/mongodb/node_modules/mongodb-core/node_modules/bson/lib/bson/parser/deserializer.js:36] [pc=0x2342c35d7d33] (this=0x1d478a704131 <undefined>,buffer=0x2b76f46bb801 <an Uint8Array with map 0x3b6adbc33909>,options=0x2b76f46bb7e1 <an Object with map 0x32e26b8e4ca1>,isArray=0x1d478a704131 <undefined>)

[flovilmart]

Stay tuned for #3080 merge, this will definitely avoir memory peaks, while letting you scale horizontally the push sending if needed.