Text processing plug in returns error when starting rapidminer studio
Joos
New Altair Community Member
This is an abstract of the error message:
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 1543503872 bytes for Failed to commit area from 0x00000005f4000000 to 0x0000000650000000 of length 1543503872.
# Possible reasons:
# The system is out of physical RAM or swap space
# In 32 bit mode, the process size limit was hit
# Possible solutions:
# Reduce memory load on the system
# Increase physical memory or swap space
# Check if swap backing store is full
# Use 64 bit Java on a 64 bit OS
# Decrease Java heap size (-Xmx/-Xms)
# Decrease number of Java threads
# Decrease Java thread stack sizes (-Xss)
# Set larger code cache with -XX:ReservedCodeCacheSize=
# This output file may be truncated or incomplete.
#
# Out of Memory Error (os_windows.cpp:3331), pid=21176, tid=0x0000000000006ab0
#
# JRE version: Java(TM) SE Runtime Environment (8.0_181-b13) (build 1.8.0_181-b13)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.181-b13 mixed mode windows-amd64 compressed oops)
# Failed to write core dump. Call to MiniDumpWriteDump() failed (Error 0x8007012b: Only part of a ReadProcessMemory or WriteProcessMemory request was completed.)
#
--------------- T H R E A D ---------------
Current thread (0x0000000011bfe800): VMThread [stack: 0x000000005beb0000,0x000000005bfb0000] [id=27312]
Stack: [0x000000005beb0000,0x000000005bfb0000]
[error occurred during error reporting (printing stack bounds), id 0xc0000005]
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
VM_Operation (0x0000000001e3e0f0): G1IncCollectionPause, mode: safepoint, requested by thread 0x0000000001e45800
--------------- P R O C E S S ---------------
Tagged:
0
Best Answer
-
I made sure it uses 64 bit java. The tool is memory expensive though and I am working on a machine together with colleagues....so making sure no one else is working in the evening did help too.2
Answers
-
hi it is fixed for now....thanks!0
-
1
-
I made sure it uses 64 bit java. The tool is memory expensive though and I am working on a machine together with colleagues....so making sure no one else is working in the evening did help too.2