Nether Crash

  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

Professor Wumbo

New Member
Jul 29, 2019
2
0
0
Might consider putting this elsewhere, but I only remember this happening with the Direwolf 20 Pack.

Memory leak upon entering the nether. Ram usage jumps to around 93%, then a spike of lag, then drops down to between 70 and 80%. Happens about every ten seconds, problem not resolved until exiting and restarting the game entirely, and staying in the overworld. Now seems to simply crash after staying in nether. If it matters, I noticed the E value on my F3 screen to be around 10000 which is pretty high.

Very very rarely do I get this problem when only in the overworld.

Ubuntu 13.04
32 bit OS
OpenJDK runtime 7, 32 bit
4GB Ram
Core i3 Processor, I think 2.4GHz
FTB Launcher version 1.3.3
Troubleshooting: tried and failed
Pastebin: http://pastebin.com/fvCHL02n (That's the FTB console log, no crash report from MC)

Hope someone can help me on this.

Mike

EDIT: Forgot to post, Direwolf20 pack, version 1.0.11. Sorry
 

JamiePhonic

New Member
Jul 29, 2019
404
0
0
your crash isnt with FTB or even java itself. the crash is happening in native code, which is causing java to crash
Code:
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x58990c05, pid=6282, tid=3060611904
#
# JRE version: 7.0_25-b30
# Java VM: OpenJDK Server VM (23.7-b01 mixed mode linux-x86 )
# Problematic frame:
# C  [libdricore9.1.7.so.1+0x14bc05]  vbo_save_unmap_vertex_store+0xce95

im not that good with linux, so i cant tell you what this relates to. sorry :/
 

Professor Wumbo

New Member
Jul 29, 2019
2
0
0
Well that complicates things. Thanks so much!

EDIT: I wonder if this is because of how Linux handles RAM, by dumping what isn't needed when memory is low. Anyone else have an idea?

Sent from my DROID RAZR HD using Tapatalk
 

JamiePhonic

New Member
Jul 29, 2019
404
0
0
I wonder if this is because of how Linux handles RAM, by dumping what isn't needed when memory is low. Anyone else have an idea?
i doubt it. i think it would only do that if you didn't set up a swap partition.
in any case, i cant find anything on google about what the cause could be.