# Javascript heap out of memeory **URL:** https://discuss.elastic.co/t/javascript-heap-out-of-memeory/200164 **Category:** Kibana **Created:** [September 19, 2019, 9:17am UTC](https://discuss.elastic.co/t/javascript-heap-out-of-memeory/200164 "2019-09-19T09:17:48Z") **Posts on this page:** 3 **Page:** 1
### Author: ![saroj\_shrestha](https://avatars.discourse-cdn.com/v4/letter/s/d26b3c/32.png) [@saroj\_shrestha](https://discuss.elastic.co/u/saroj_shrestha) #### Post date: [September 19, 2019, 9:17am UTC](https://discuss.elastic.co/t/javascript-heap-out-of-memeory/200164/1 "2019-09-19T09:17:48Z")
Hey guys. Have you faced "Javascript heap out of memory" after you have increased the heap size for the nodejs. ![image](https://us1.discourse-cdn.com/elastic/original/3X/a/8/a872767e6b10bec025b2841d15cfb454795599c5.png) ![image](https://us1.discourse-cdn.com/elastic/original/3X/c/5/c50b1cadaa960a291af8e627f4e9102f383a1be5.png) ---
### Author: ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley) #### Post date: [September 19, 2019, 9:46pm UTC](https://discuss.elastic.co/t/javascript-heap-out-of-memeory/200164/2 "2019-09-19T21:46:18Z")
Because the optimization is running in another process it's not actually seeing the increased heap size. What branch is this based off of? A few months ago we increased it for the builds here, which should be enough: > Might just need to apply that change to what you're working on. ---
### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system) #### Post date: [October 17, 2019, 9:46pm UTC](https://discuss.elastic.co/t/javascript-heap-out-of-memeory/200164/3 "2019-10-17T21:46:21Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.