mojira.dev

In Minecraft 1.9 Prerelease 4, entering the Nether leads to a massive memory leak. This manifests as intense lag which starts as unplayable and then continues to get worse, until it's completely locked up, and after killing the process the log contains this error:

[03:32:12] [Server thread/ERROR]: Encountered an unexpected exception
java.lang.OutOfMemoryError: Java heap space
at ass.a(SourceFile:203) ~[1.9-pre4.jar:?]
at ass.a(SourceFile:102) ~[1.9-pre4.jar:?]
at lo.b(SourceFile:147) ~[1.9-pre4.jar:?]
at lo.a(SourceFile:166) ~[1.9-pre4.jar:?]
at lp.a(SourceFile:885) ~[1.9-pre4.jar:?]
at net.minecraft.server.MinecraftServer.a(SourceFile:371) ~[1.9-pre4.jar:?]
at byn.a(SourceFile:213) ~[1.9-pre4.jar:?]
at net.minecraft.server.MinecraftServer.C(SourceFile:571) ~[1.9-pre4.jar:?]
at byn.C(SourceFile:154) ~[1.9-pre4.jar:?]
at net.minecraft.server.MinecraftServer.run(SourceFile:457) [1.9-pre4.jar:?]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_71]

My computer isn't the beefiest machine (a laptop with 8GB of RAM), but never in any previous versions has it even lagged noticeably in the Nether, and it certainly shouldn't be running out of heap memory and crashing just from entering the dimension.

To reproduce:

1) Create a new world in 1.9 pre 4.
2) Create a Nether portal.
3) Enter the portal, notice the lag, and wait as the lag gets worse and worse until it ultimately locks up.

(Note: this occurs in at least creative and survival mode; I'm not sure about spectator mode or, probably more relevantly, spectator mode without spectator chunk generation.)

Comments 6

Before entering the nether:

Please force a crash by pressing F3 + C for 10 seconds while in-game and attach the crash report ([minecraft/crash-reports/crash-<DATE>-client.txt|http://hopper.minecraft.net/help/finding-minecraft-data-folder]) to this ticket.

The attachments form isn't working for me (when I submit it, it clears the file input and asks me to select a file again). Hopefully it's okay if I just copy/paste the file contents here.


Minecraft Crash Report ----
// You're mean.

Time: 2/27/16 3:51 AM
Description: Manually triggered debug crash

java.lang.Throwable
at bcf.az(SourceFile:1694)
at bcf.t(SourceFile:1615)
at bcf.av(SourceFile:962)
at bcf.a(SourceFile:392)
at net.minecraft.client.main.Main.main(SourceFile:124)

A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

– Head –
Stacktrace:
at bcf.az(SourceFile:1694)

– Affected level –
Details:
Level name: MpServer
All players: 1 total; [bmt['IceMetalPunk'/24, l='MpServer', x=2133.50, y=5.79, z=67.50]]
Chunk stats: MultiplayerChunkCache: 3968, 3968
Level seed: 0
Level generator: ID 01 - flat, ver 0. Features enabled: false
Level generator options:
Level spawn location: World: (2137,4,59), Chunk: (at 9,0,11 in 133,3; contains blocks 2128,0,48 to 2143,255,63), Region: (4,0; contains chunks 128,0 to 159,31, blocks 2048,0,0 to 2559,255,511)
Level time: 1057 game time, 1057 day time
Level dimension: 0
Level storage version: 0x00000 - Unknown?
Level weather: Rain time: 0 (now: false), thunder time: 0 (now: false)
Level game mode: Game mode: creative (ID 1). Hardcore: false. Cheats: false
Forced entities: 49 total; [we['Sheep'/78976, l='MpServer', x=2192.82, y=4.00, z=49.77], yx['Slime'/65026, l='MpServer', x=2200.50, y=4.00, z=69.84], yx['Slime'/133252, l='MpServer', x=2092.63, y=4.53, z=84.97], yx['Slime'/119302, l='MpServer', x=2179.95, y=4.72, z=0.38], yx['Slime'/180744, l='MpServer', x=2098.15, y=4.72, z=67.99], wc['Pig'/78989, l='MpServer', x=2058.50, y=4.00, z=43.50], vy['Cow'/78991, l='MpServer', x=2061.50, y=4.00, z=41.50], wc['Pig'/78990, l='MpServer', x=2061.50, y=4.00, z=44.50], vy['Cow'/78992, l='MpServer', x=2059.50, y=4.00, z=43.50], bmt['IceMetalPunk'/24, l='MpServer', x=2133.50, y=5.79, z=67.50], yx['Slime'/16927, l='MpServer', x=2074.13, y=4.00, z=35.15], yx['Slime'/42026, l='MpServer', x=2083.51, y=4.04, z=62.36], yx['Slime'/66608, l='MpServer', x=2183.02, y=4.14, z=118.96], yx['Slime'/115770, l='MpServer', x=2083.26, y=4.00, z=80.78], we['Sheep'/78925, l='MpServer', x=2108.50, y=4.00, z=7.50], we['Sheep'/78924, l='MpServer', x=2107.50, y=4.00, z=7.50], we['Sheep'/78927, l='MpServer', x=2113.50, y=4.00, z=10.50], we['Sheep'/78926, l='MpServer', x=2113.50, y=4.00, z=8.50], we['Sheep'/78933, l='MpServer', x=2079.88, y=4.00, z=131.36], we['Sheep'/78932, l='MpServer', x=2082.50, y=4.00, z=126.50], we['Sheep'/78935, l='MpServer', x=2076.69, y=4.00, z=123.80], we['Sheep'/78934, l='MpServer', x=2085.38, y=4.00, z=123.81], we['Sheep'/78937, l='MpServer', x=2152.50, y=4.00, z=34.12], yx['Slime'/179418, l='MpServer', x=2081.57, y=4.00, z=68.37], we['Sheep'/78936, l='MpServer', x=2152.50, y=4.00, z=33.05], we['Sheep'/78939, l='MpServer', x=2153.50, y=4.00, z=33.50], yx['Slime'/115931, l='MpServer', x=2077.02, y=5.17, z=92.46], we['Sheep'/78938, l='MpServer', x=2152.50, y=4.00, z=35.50], vy['Cow'/78941, l='MpServer', x=2190.50, y=4.00, z=99.50], vy['Cow'/78940, l='MpServer', x=2190.50, y=4.00, z=101.50], vy['Cow'/78943, l='MpServer', x=2185.50, y=4.00, z=95.50], vy['Cow'/78942, l='MpServer', x=2192.16, y=4.00, z=98.49], yx['Slime'/194664, l='MpServer', x=2092.99, y=4.00, z=69.88], vx['Chicken'/78957, l='MpServer', x=2164.50, y=4.00, z=-5.50], yx['Slime'/136174, l='MpServer', x=2192.12, y=4.00, z=11.75], vx['Chicken'/78958, l='MpServer', x=2166.50, y=4.00, z=-3.50], vy['Cow'/78961, l='MpServer', x=2071.42, y=4.00, z=35.41], vy['Cow'/78960, l='MpServer', x=2074.50, y=4.00, z=30.50], we['Sheep'/78963, l='MpServer', x=2074.50, y=4.00, z=29.50], we['Sheep'/78962, l='MpServer', x=2077.50, y=4.00, z=25.50], we['Sheep'/78969, l='MpServer', x=2153.50, y=4.00, z=121.50], we['Sheep'/78968, l='MpServer', x=2153.50, y=4.00, z=117.50], wc['Pig'/78971, l='MpServer', x=2163.25, y=4.00, z=108.67], we['Sheep'/78970, l='MpServer', x=2152.50, y=4.00, z=118.50], yx['Slime'/189945, l='MpServer', x=2165.25, y=4.27, z=18.94], wk['Horse'/78973, l='MpServer', x=2198.50, y=4.00, z=55.50], wk['Horse'/78972, l='MpServer', x=2198.50, y=4.00, z=52.50], wk['Horse'/78975, l='MpServer', x=2196.15, y=4.00, z=52.15], wk['Horse'/78974, l='MpServer', x=2190.06, y=4.00, z=47.15]]
Retry entities: 0 total; []
Server brand: vanilla
Server type: Integrated singleplayer server
Stacktrace:
at bku.a(SourceFile:365)
at bcf.b(SourceFile:2515)
at bcf.a(SourceFile:401)
at net.minecraft.client.main.Main.main(SourceFile:124)

– System Details –
Details:
Minecraft Version: 1.9-pre4
Operating System: Windows 8.1 (amd64) version 6.3
Java Version: 1.8.0_71, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 655083336 bytes (624 MB) / 1040543744 bytes (992 MB) up to 1060372480 bytes (1011 MB)
JVM Flags: 6 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx1G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
Launched Version: 1.9-pre4
LWJGL: 2.9.4
OpenGL: Intel(R) HD Graphics 4600 GL version 4.2.0 - Build 10.18.10.3345, Intel
GL Caps: Using GL 1.3 multitexturing.
Using GL 1.3 texture combiners.
Using framebuffer objects because OpenGL 3.0 is supported and separate blending is supported.
Shaders are available because OpenGL 2.1 is supported.
VBOs are available because OpenGL 1.5 is supported.

Using VBOs: No
Is Modded: Probably not. Jar signature remains and client brand is untouched.
Type: Client (map_client.txt)
Resource Packs: Ashiok, ClearGlass1.9
Current Language: English (US)
Profiler Position: N/A (disabled)
CPU: 4x Intel(R) Core(TM) i3-4000M CPU @ 2.40GHz

Memory: 655083336 bytes (624 MB) / 1040543744 bytes (992 MB) up to 1060372480 bytes (1011 MB)

Your memory allocation is near the maximum, assign more RAM to Minecraft, see MC-12949

Ah. That fixed it; I don't know why I didn't try that in the first place. Did I just happen to get a string of unlucky seeds here, or has something changed in pre-4 that's increased the amount of memory Nether generation requires?

IMO 1.9 has a higher memory consumption in the Nether.

Well, that's unfortunate for my little machine 😞 Ah, well. Thanks for the quick help resolving this.

Daniel Burnett

(Unassigned)

Unconfirmed

crash, lag, memory-leak, nether

Minecraft 1.9 Pre-Release 4

Retrieved