# KNIME Analytics platform crash

**URL:** <https://forum.knime.com/t/knime-analytics-platform-crash/13255>\
**Category:** KNIME Analytics Platform\
**Created:** [January 23, 2019, 2:02pm UTC](https://forum.knime.com/t/knime-analytics-platform-crash/13255 "2019-01-23T14:02:03Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ipazin](https://forum-cdn.knime.com/user_avatar/forum.knime.com/ipazin/32/806_2.png) [@ipazin](https://forum.knime.com/u/ipazin)\
**Post date:** [January 23, 2019, 3:41pm UTC](https://forum.knime.com/t/knime-analytics-platform-crash/13255/2 "2019-01-23T15:41:46Z")

</div>

Hi there!

Reduced RAM? I would increase it…  
Also check this replay:

> [@KNIME crashes with 6000x6000 table](https://forum.knime.com/t/knime-crashes-with-6000x6000-table/13143/4):
>
> If this is not related to problems we are seeing with Loops in the latest KNIME release 3.7 you could check out the various hints concerning KNIME performance. It could make sense to try and split the workflow up into several parts and see if that makes any difference. You could also try and monitor the Java Heap Space and see when that reaches a critical point. KNIME performance

Br,  
Ivan

---

_[View the full topic](https://forum.knime.com/t/knime-analytics-platform-crash/13255)._