[ https://issues.apache.org/jira/browse/IGNITE-5618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16224619#comment-16224619 ]
Pavel Tupitsyn edited comment on IGNITE-5618 at 10/30/17 10:22 AM: ------------------------------------------------------------------- [~dpavlov] it still crashes under 32-bit JDK on 64-bit machine. Steps to reproduce (on Windows): * Download binary release of ignite-2.3 and unzip * Download and install 32-bit Oracle JDK * Make sure {{JAVA_HOME}} points to that 32-bit JDK * Run {{ignite.bat}}, it fails with OOM We have reduced default region size to 20% of total physical memory. I have 16 GB of RAM, this results in default region max size of 3.2 GB, which is too much for a 32-bit process. was (Author: ptupitsyn): [~dpavlov] it still crashes under 32-bit JDK on 64-bit machine. Steps to reproduce (on Windows): * Download binary release of ignite-2.3 and unzip * Download and install 32-bit Oracle JDK * Make sure {{JAVA_HOME}} points to that 32-bit JDK * Run {{ignite.bat}}, it fails with OOM > .NET: Ignite fails with OOM on startup under x86 (32 bit) with default > configuration > ------------------------------------------------------------------------------------ > > Key: IGNITE-5618 > URL: https://issues.apache.org/jira/browse/IGNITE-5618 > Project: Ignite > Issue Type: Bug > Components: platforms > Affects Versions: 2.0 > Reporter: Pavel Tupitsyn > Priority: Blocker > Labels: .NET, MakeTeamcityGreenAgain > > Default MemoryPolicyConfiguration settings do not take process bitness into > account. We can't use 80% of RAM under 32-bit mode. > * Add a suite on TC which runs .NET tests on 32 bits -- This message was sent by Atlassian JIRA (v6.4.14#64029)