# Kibana 6.5.0 Javascript heap out of memory

**URL:** https://discuss.elastic.co/t/kibana-6-5-0-javascript-heap-out-of-memory/157365
**Category:** Kibana
**Created:** [November 19, 2018, 1:24pm UTC](https://discuss.elastic.co/t/kibana-6-5-0-javascript-heap-out-of-memory/157365 "2018-11-19T13:24:24Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![drjackal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/drjackal/32/33187_2.png) [@drjackal](https://discuss.elastic.co/u/drjackal)
#### Post date: [November 19, 2018, 1:24pm UTC](https://discuss.elastic.co/t/kibana-6-5-0-javascript-heap-out-of-memory/157365/1 "2018-11-19T13:24:24Z")

</div>

Hi all,

I have installed Kibana 6.5.0 to replace 6.4.0 on my Windows box.  
After starting Kibana now says  
Optimizing and caching bundles for ml, stateSessionStorageRedirect, status\_page, timelion, graph, monitoring, space\_selector, login, logout, dashboardViewer, apm, canvas, infra and kibana. This may take a few minutes.

This takes a while and then Kibana quits with the following error:

\<--- Last few GCs ---\>

[7816:0000027E4246DF80] 1135506 ms: Mark-sweep 1310.1 (1433.8) -\> 1310.1 (1434.8) MB, 1717.6 / 0.0 ms allocation failure GC in old space requested  
[7816:0000027E4246DF80] 1137275 ms: Mark-sweep 1310.1 (1434.8) -\> 1310.1 (1418.3) MB, 1769.1 / 0.0 ms last resort GC in old space requested  
[7816:0000027E4246DF80] 1139281 ms: Mark-sweep 1310.1 (1418.3) -\> 1310.1 (1418.3) MB, 2005.5 / 0.0 ms last resort GC in old space requested

\<--- JS stacktrace ---\>

==== JS stack trace =========================================

Security context: 0000026F7E7A5879   
0: builtin exit frame: lastIndexOf(this=0000034320F2E461 \<Very long string[5037308]\>,0000033505F8CA51 \<String[1]: \n\>)

1: has\_nlb(aka has\_nlb) [000001A94B0022D1 :5970] [bytecode=000001D6CB3361C9 offset=15](this=000001A94B0022D1 )  
2: /\* anonymous _/(aka /_ anonymous \*/) [000001A94B0022D1 :6070] [bytecode=000003ED772A0AF9 offset=60](this=000001A94B0...

FATAL ERROR: CALL\_AND\_RETRY\_LAST Allocation failed - JavaScript heap out of memory  
1: node\_module\_register  
2: v8::internal::FatalProcessOutOfMemory  
3: v8::internal::FatalProcessOutOfMemory  
4: v8::internal:: Factory::NewRawTwoByteString  
5: v8::internal::Smi::SmiPrint  
6: v8::internal::StackGuard::HandleInterrupts  
7: v8::internal::SlicedString::SlicedStringGet  
8: v8\_inspector::protocol::Debugger::API::SearchMatch::fromJSONString  
9: v8\_inspector::protocol::Debugger::API::SearchMatch::fromJSONString  
10: 0000010D32C06B21

I can imagine that I have to increase the java heap size. But how to do this on my Windows box?

Any help is highly appreciated.  
Jack

---

<div class="post-metadata">

### Author: ![thomasneirynck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thomasneirynck/32/23313_2.png) [@thomasneirynck](https://discuss.elastic.co/u/thomasneirynck)
#### Post date: [November 19, 2018, 8:07pm UTC](https://discuss.elastic.co/t/kibana-6-5-0-javascript-heap-out-of-memory/157365/2 "2018-11-19T20:07:41Z")

</div>

hi @drjackal,

actually, it's the nodejs heap you'd have to increase. you should not have to touch your JVM.

you can pass in the NODE\_OPTIONS when starting kibana.

see [https://github.com/elastic/kibana/issues/1924#issuecomment-399376071](https://github.com/elastic/kibana/issues/1924#issuecomment-399376071) for details.

Restarting Kibana sometimes does the trick to, YMMV.

---

<div class="post-metadata">

### Author: ![drjackal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/drjackal/32/33187_2.png) [@drjackal](https://discuss.elastic.co/u/drjackal)
#### Post date: [November 20, 2018, 3:50pm UTC](https://discuss.elastic.co/t/kibana-6-5-0-javascript-heap-out-of-memory/157365/3 "2018-11-20T15:50:34Z")

</div>

Well, @thomasneirynck, that did the job.

I started node.exe manually with --max\_old\_space\_size=4096 and Kibana started and optimized the bundles. (node.exe" --max\_old\_space\_size=4096 --no-warnings "D:\ELK-Stack\kibana-6.5.0\src\cli")  
Now I can start kibana without add --max\_old\_space\_size=4096.

Thank you!

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [December 18, 2018, 3:50pm UTC](https://discuss.elastic.co/t/kibana-6-5-0-javascript-heap-out-of-memory/157365/4 "2018-12-18T15:50:38Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.