Ftb Crash - Mc process exit - rtn 137

[LantzR]

Title:

Ftb Crash - Mc process exit - rtn 137​

Launcher Version:

latest stable​

Modpack:

Direwolf20 1.7.10​

Modpack Version:

​

Log Link:

​

Details of the issue:

=== LantzR Notes ==

- Ftb_Tail.txt (self) - http://pastebin.com/YzhRge5J
- MinecraftLog.txt - http://pastebin.com/kRxw4UFp
- FtbLauncherLog.txt - http://pastebin.com/8qFfDgpV

# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
@h@[21:49:52] [INFO] MCLauncher.launchMinecraft:87:
@h@ Pack: FTB Presents Direwolf20 1.7.10
[21:49:52] [INFO] MCLauncher.setMemory:269: Setting MinMemory to 256
[21:49:52] [INFO] MCLauncher.setMemory:271: Setting MaxMemory to 2816
[21:49:52] [INFO] MCLauncher.launchMinecraft:110: Defaulting PermSize to 256m
[21:49:52] [INFO] MCLauncher.launchMinecraft:136:
Additional java parameters: -Xmx2800M -Xms2800M -XX:MaxPermSize=256M
[21:49:52] [DEBUG] MCInstaller.launchMinecraft:428: MC PID: 6456
[21:49:53] [DEBUG] Benchmark.logBenchAs:73: UnreadNews Init took 10 ms.
@h@[22:40:20] [INFO] ProcessMonitor.run:43: MC process exited. return value: 137
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Thanks,
Lantz​

 

[LantzR]

... <waiting> ...

So when does code 137 get returned?

 

[jikuja]

... <waiting> ...

So when does code 137 get returned?

Not going to use time for that question...
"[INFO] MainHelpers.printInfo:49: System memory: 1888M free, 2940M total" vs "[INFO] MCLauncher.launchMinecraft:136: Additional java parameters: -Xmx2800M -Xms2800M -XX:MaxPermSize=256M" Rethink memory allocation. Current allocation might work but also might cause problems.