The Meaning of Life, the Universe, and Everything.
Join Date:
4/27/2011
Posts:
154
Minecraft:
Vahkiti
Xbox:
Vahkiti
PSN:
Vahkiti
Member Details
Hi guys! So I recently started exploring one of my old worlds again, and when I go over seemingly random locations in the map, I get the following error following a crash:
---- Minecraft Crash Report ----
// Don't do that.
java.lang.IllegalArgumentException: n must be positive
at java.util.Random.nextInt(Unknown Source)
at agr.a(SourceFile:176)
at agr.a(SourceFile:27)
at agl.a(SourceFile:364)
at agt.a(SourceFile:29)
at apq.a(SourceFile:432)
at ml.a(SourceFile:160)
at aoo.a(SourceFile:781)
at ml.c(SourceFile:95)
at mk.<init>(SourceFile:36)
at mj.a(SourceFile:217)
at mj.a(SourceFile:254)
at lg.a(SourceFile:155)
at lg.c(SourceFile:206)
at lg.a(SourceFile:100)
at ng.c(SourceFile:87)
at ng.a(SourceFile:52)
at ef.a(SourceFile:166)
at mv.c(SourceFile:134)
at net.minecraft.server.MinecraftServer.u(SourceFile:528)
at net.minecraft.server.MinecraftServer.t(SourceFile:440)
at btk.t(SourceFile:117)
at net.minecraft.server.MinecraftServer.run(SourceFile:357)
at lb.run(SourceFile:616)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Stacktrace:
at java.util.Random.nextInt(Unknown Source)
at agr.a(SourceFile:176)
at agr.a(SourceFile:27)
at agl.a(SourceFile:364)
at agt.a(SourceFile:29)
at apq.a(SourceFile:432)
at ml.a(SourceFile:160)
at aoo.a(SourceFile:781)
at ml.c(SourceFile:95)
at mk.<init>(SourceFile:36)
at mj.a(SourceFile:217)
at mj.a(SourceFile:254)
at lg.a(SourceFile:155)
at lg.c(SourceFile:206)
at lg.a(SourceFile:100)
at ng.c(SourceFile:87)
at ng.a(SourceFile:52)
at ef.a(SourceFile:166)
-- Ticking connection --
Details:
Connection: [email protected]
Stacktrace:
at mv.c(SourceFile:134)
at net.minecraft.server.MinecraftServer.u(SourceFile:528)
at net.minecraft.server.MinecraftServer.t(SourceFile:440)
at btk.t(SourceFile:117)
at net.minecraft.server.MinecraftServer.run(SourceFile:357)
at lb.run(SourceFile:616)
-- System Details --
Details:
Minecraft Version: 1.7.4
Operating System: Windows 8 (amd64) version 6.2
Java Version: 1.7.0_45, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 209104240 bytes (199 MB) / 380108800 bytes (362 MB) up to 954728448 bytes (910 MB)
JVM Flags: 2 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx1G
AABB Pool Size: 1904 (106624 bytes; 0 MB) allocated, 1904 (106624 bytes; 0 MB) used
IntCache: cache: 0, tcache: 0, allocated: 12, tallocated: 94
Profiler Position: N/A (disabled)
Vec3 Pool Size: 247 (13832 bytes; 0 MB) allocated, 247 (13832 bytes; 0 MB) used
Player Count: 1 / 8; [mp['Vahkiti'/137, l='Chi-Chitopia', x=-2621.48, y=124.98, z=-1576.87]]
Type: Integrated Server (map_client.txt)
Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.
Occasionally the description will be different and slightly more descriptive, saying instead: "Exception getting block type in world". Since it continues to plague me even after reinstalling Minecraft, I can't figure out what it might be since I haven't ever used custom blocks in this map. Even if I had, I doubt they'd cause a crash like this.
The bug first appeared when I was attempting to re-map the world a few days ago. it had never happened before, and at the time, the world had holes leading to the void, so I figured that was the cause of the problem as previously, maps were unable to handle exposed void and would cause a crash. So I opened up MCEdit and set to work closing all that off. Evidently, that was not in fact the cause of the issue and I am currently out of ideas.
I'm currently running on the following system specs:
// Don't do that.
Time: 03/01/14 17:13
Description: Ticking memory connection
java.lang.IllegalArgumentException: n must be positive
at java.util.Random.nextInt(Unknown Source)
at agr.a(SourceFile:176)
at agr.a(SourceFile:27)
at agl.a(SourceFile:364)
at agt.a(SourceFile:29)
at apq.a(SourceFile:432)
at ml.a(SourceFile:160)
at aoo.a(SourceFile:781)
at ml.c(SourceFile:95)
at mk.<init>(SourceFile:36)
at mj.a(SourceFile:217)
at mj.a(SourceFile:254)
at lg.a(SourceFile:155)
at lg.c(SourceFile:206)
at lg.a(SourceFile:100)
at ng.c(SourceFile:87)
at ng.a(SourceFile:52)
at ef.a(SourceFile:166)
at mv.c(SourceFile:134)
at net.minecraft.server.MinecraftServer.u(SourceFile:528)
at net.minecraft.server.MinecraftServer.t(SourceFile:440)
at btk.t(SourceFile:117)
at net.minecraft.server.MinecraftServer.run(SourceFile:357)
at lb.run(SourceFile:616)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Stacktrace:
at java.util.Random.nextInt(Unknown Source)
at agr.a(SourceFile:176)
at agr.a(SourceFile:27)
at agl.a(SourceFile:364)
at agt.a(SourceFile:29)
at apq.a(SourceFile:432)
at ml.a(SourceFile:160)
at aoo.a(SourceFile:781)
at ml.c(SourceFile:95)
at mk.<init>(SourceFile:36)
at mj.a(SourceFile:217)
at mj.a(SourceFile:254)
at lg.a(SourceFile:155)
at lg.c(SourceFile:206)
at lg.a(SourceFile:100)
at ng.c(SourceFile:87)
at ng.a(SourceFile:52)
at ef.a(SourceFile:166)
-- Ticking connection --
Details:
Connection: [email protected]
Stacktrace:
at mv.c(SourceFile:134)
at net.minecraft.server.MinecraftServer.u(SourceFile:528)
at net.minecraft.server.MinecraftServer.t(SourceFile:440)
at btk.t(SourceFile:117)
at net.minecraft.server.MinecraftServer.run(SourceFile:357)
at lb.run(SourceFile:616)
-- System Details --
Details:
Minecraft Version: 1.7.4
Operating System: Windows 8 (amd64) version 6.2
Java Version: 1.7.0_45, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 209104240 bytes (199 MB) / 380108800 bytes (362 MB) up to 954728448 bytes (910 MB)
JVM Flags: 2 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx1G
AABB Pool Size: 1904 (106624 bytes; 0 MB) allocated, 1904 (106624 bytes; 0 MB) used
IntCache: cache: 0, tcache: 0, allocated: 12, tallocated: 94
Profiler Position: N/A (disabled)
Vec3 Pool Size: 247 (13832 bytes; 0 MB) allocated, 247 (13832 bytes; 0 MB) used
Player Count: 1 / 8; [mp['Vahkiti'/137, l='Chi-Chitopia', x=-2621.48, y=124.98, z=-1576.87]]
Type: Integrated Server (map_client.txt)
Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.
Occasionally the description will be different and slightly more descriptive, saying instead: "Exception getting block type in world". Since it continues to plague me even after reinstalling Minecraft, I can't figure out what it might be since I haven't ever used custom blocks in this map. Even if I had, I doubt they'd cause a crash like this.
The bug first appeared when I was attempting to re-map the world a few days ago. it had never happened before, and at the time, the world had holes leading to the void, so I figured that was the cause of the problem as previously, maps were unable to handle exposed void and would cause a crash. So I opened up MCEdit and set to work closing all that off. Evidently, that was not in fact the cause of the issue and I am currently out of ideas.
I'm currently running on the following system specs:
CPU: DualCore Intel Pentium E5300, 2600 MHz
Motherboard: Intel Eaglelake G41
GPU: NVIDIA GeForce GTX 550 Ti
Resolution: 1280x1024
Ram: 4GB (2GB x2)
OS: Windows 8.1 (x64)
Anyone else have a thought of what could be happening here? Any assistance would be much appreciated.