# Elasticsearch1.4.4 always oom，we suspected nested object

**URL:** <https://discuss.elastic.co/t/elasticsearch1-4-4-always-oom-we-suspected-nested-object/23184>\
**Category:** Elasticsearch\
**Created:** [April 10, 2015, 2:04pm UTC](https://discuss.elastic.co/t/elasticsearch1-4-4-always-oom-we-suspected-nested-object/23184 "2015-04-10T14:04:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![stoneling](https://avatars.discourse-cdn.com/v4/letter/s/dec6dc/32.png) [@stoneling](https://discuss.elastic.co/u/stoneling)\
**Post date:** [April 10, 2015, 2:04pm UTC](https://discuss.elastic.co/t/elasticsearch1-4-4-always-oom-we-suspected-nested-object/23184/1 "2015-04-10T14:04:37Z")

</div>

Ees1.4.4 appear oom 。According to the dump，we found a big object ,so we suspected that the nested object caused this phenomenon. I hope that you can tell me how to avoid this problem and we idea is true or not ,thanks.66stances of "org.elasticsearch.index.cache.fixedbitset.FixedBitSetFilterCache",loaded by "sun.misc.Launcher$AppClassLoader@0x7f8b7d3d20f8" occupy 17,351,214,92(54.14%) byte.\<nabble\_img src="215.jpg" border="0" class="left"/\>\<nabble\_img src="216.jpg" border="0" class="left"/\>

---

<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:** [July 6, 2017, 12:20am UTC](https://discuss.elastic.co/t/elasticsearch1-4-4-always-oom-we-suspected-nested-object/23184/2 "2017-07-06T00:20:23Z")

</div>

Closed on July 6, 2017, 12:20am UTC