)
2: size [0x1ab23cd1c1e1] [/kibana/kibana-7.6.0-linux-x86\_64/node\_modules/hapi/lib/response.js:682] [bytecode=0x188f...
FATAL ERROR: CALL\_AND\_RETRY\_LAST Allocation failed - JavaScript heap out of memory
......
......
This occurred after adding the max-old-space-size=2048 to bin/kibana.
Anyone has another suggestion?
Thanks!
Vee
---
### Author:  [@joshdover](https://discuss.elastic.co/u/joshdover)
#### Post date: [August 17, 2020, 11:07pm UTC](https://discuss.elastic.co/t/check-kibana-max-old-space-size/245310/5 "2020-08-17T23:07:17Z")
I'm not aware of any way to verify the setting is being picked up. This setting is passed from Node.js into V8 (the JavaScript engine) directly, so there may be a way get this information out via V8's debugging API.
That said, I would try increasing this limit until you see the problem go away. If that doesn't work then it's not being set correctly. You can also set it when you execute Kibana:
```auto
NODE_OPTIONS="--max-old-space-size=4096" ./bin/kibana
```
Is there anything that seems to trigger this failure? For example, does this always happen on startup or when using a particular feature? It's possible you've encountered a bug in a feature that is creating very large amounts of memory usage that cannot be fixed by increasing this limit.
---
### Author:  [@VeeT](https://discuss.elastic.co/u/VeeT)
#### Post date: [August 18, 2020, 2:40pm UTC](https://discuss.elastic.co/t/check-kibana-max-old-space-size/245310/6 "2020-08-18T14:40:12Z")
Josh,
Thanks. I will try adding it on the command line..
It seems like this failure is triggered when a query is run that returns a big result. It's hard to troubleshoot given the limited error log we see.
-Vee
---
### Author:  [@joshdover](https://discuss.elastic.co/u/joshdover)
#### Post date: [August 19, 2020, 4:03pm UTC](https://discuss.elastic.co/t/check-kibana-max-old-space-size/245310/7 "2020-08-19T16:03:48Z")
If a specific query is triggering the problem, you may want to try upgrading the Stack. We have fixed issues like this in the past and it's possible there is a bug fix for your specific issue. Do you know where these queries are originating from (Discover, Dashboard, Canvas, etc.)?
---
### Author:  [@VeeT](https://discuss.elastic.co/u/VeeT)
#### Post date: [September 11, 2020, 8:25pm UTC](https://discuss.elastic.co/t/check-kibana-max-old-space-size/245310/8 "2020-09-11T20:25:49Z")
Josh,
I'm still trying to figure out where the query is being executed from. Is there a way to tell where it's coming from?
Thanks!
Vee
---
### Author:  [@joshdover](https://discuss.elastic.co/u/joshdover)
#### Post date: [September 14, 2020, 11:32pm UTC](https://discuss.elastic.co/t/check-kibana-max-old-space-size/245310/9 "2020-09-14T23:32:23Z")
Your best be is turn on query logging by adding these to your kibana.yml file and restarting Kibana:
```auto
elasticsearch.logQueries: true
logging.verbose: true
```
You then should be able to see which query happens just before Kibana crashes. I hope that is helpful!
---
### Author:  [@VeeT](https://discuss.elastic.co/u/VeeT)
#### Post date: [September 15, 2020, 2:45pm UTC](https://discuss.elastic.co/t/check-kibana-max-old-space-size/245310/10 "2020-09-15T14:45:13Z")
Will try this. Thanks Josh!
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 13, 2020, 2:45pm UTC](https://discuss.elastic.co/t/check-kibana-max-old-space-size/245310/11 "2020-10-13T14:45:23Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.