Crash: IndexOutOfBoundsException on Tesselating block in world
When ever I load a certain area of my world the attached crash happens.
If the world is started as a server only the client crashes, but the crash report should speak for itself.
Steps to reproduce:
1. Download the attached world file
2. Log into this world
3. Look down
Description: Tesselating block in world java.lang.IndexOutOfBoundsException at java.nio.Buffer.checkIndex(Buffer.java:538) at java.nio.DirectByteBuffer.putFloat(DirectByteBuffer.java:887) at bfd.b(SourceFile:414) at bge.a(SourceFile:225) at bgd.a(SourceFile:67) at bht.b(SourceFile:176) at bhp.a(SourceFile:78) at bho.b(SourceFile:121) at bfr.a(SourceFile:842)
Note that this crash might be environment dependent.
How the world got corrupted like this
I had the world open to LAN and when I left it Minecraft hung (MC-72943). After forcing the process to stop and restarting the crash happened when ever joining the world again.
Search disclaimer
The only unresolved issue I could find which might be related to this one is MC-81252, but it has a completely different stack trace. There is many other issues about the same/similar crashes but as they are resolved I just assume that they have different causes.
Potential Fix
The reason for the exception is that a buffer for rendering overflows.
package net.minecraft.client.renderer; ... public class WorldRenderer { ... private void growBuffer(int p_178983_1_) { LogManager.getLogger().warn("Needed to grow BufferBuilder buffer: Old size " + this.bufferSize * 4 + " bytes, new size " + (this.bufferSize * 4 + p_178983_1_) + " bytes."); this.bufferSize += p_178983_1_ / 4; ByteBuffer var2 = GLAllocation.createDirectByteBuffer(this.bufferSize * 4); this.rawIntBuffer.position(0); var2.asIntBuffer().put(this.rawIntBuffer); this.byteBuffer = var2; this.rawIntBuffer = this.byteBuffer.asIntBuffer(); this.rawFloatBuffer = this.byteBuffer.asFloatBuffer(); } public void setVertexState(WorldRenderer.State p_178993_1_) { this.rawIntBuffer.clear(); // This call causes the crash. Calling growBuffer() when needed fixes the crash for me. this.rawIntBuffer.put(p_178993_1_.func_179013_a()); this.rawBufferIndex = p_178993_1_.getRawBufferIndex(); this.vertexCount = p_178993_1_.getVertexCount(); this.vertexFormat = new VertexFormat(p_178993_1_.func_179016_d()); } ... }
Growing the buffer might be the right fix, but it could also be that the reason why it overflows is a bug in the first place.
Environment
Operating System: Linux (amd64) version 3.13.0-55-lowlatency
Java Version: 1.7.0_79, Oracle Corporation
Java VM Version: OpenJDK 64-Bit Server VM (mixed mode), Oracle Corporation
Linked Issues
is duplicated by7
MC-81261When in a certain area, crashs.DuplicateMC-81898crashes every time i join the server DuplicateMC-89089Description: Tesselating block in worldDuplicateMC-89110---- Minecraft Crash Report ----DuplicateMC-89321Tesselating Block in World crashDuplicateMC-94402cant even move bofore i get kicked,DuplicateMC-94403Crash: java.lang.IndexOutOfBoundsExceptionDuplicate
![[Mojang] Panda](../../../data/avatars/users/41658.png){kind=small}
Created Issue:
IndexOutOfBoundsException on Tesselating block in world
When ever I load a certain area of my world the attached crash happens.
If the world is started as a server only the client crashes, but the crash report should speak for itself.Steps to reproduce:
1. Download the attached world file
2. Log into this world
3. Look downNote that this crash might be environment dependent.
How the world got corrupted like this
I had the world open to LAN and when I left it Minecraft hung (Which should be covered in a different bug report, when there is any way to reproduce it). After forcing the process to stop and restarting the crash happened when ever joining the world again.Search disclaimer
The only unresolved issue I could find which might be related to this one isMC-81252, but it has a completely different stack trace. There is many other issues about the same/similar crashes but as they are resolved I just assume that they have different causes.How I fixed the corrupted world
To be able to play in this world again, I started it up on a server with render distance 16.
Then I connected with a client on render distance 2 and went so close to the corrupted blocks that they were loaded but didn't get rendered. (An other way to do this is probably to just look in an other direction).
As the crash report tells me which blocks it crashes on (water blocks around 5248,85,2331), I replaced all the blocks the crash happened on with something else:
/fill 5243 64 2331 5272 128 2331 minecraft:stone_slab 0 replace minecraft:water 7
After that I went in the area and no crash happened any more.
To undo the change I replaced all the slabs with water again:
/fill 5243 64 2331 5272 128 2331 minecraft:water 7 replace minecraft:stone_slab 0Environment
– System Details –
Details:
Minecraft Version: 1.8.7
Operating System: Linux (amd64) version 3.13.0-55-lowlatency
CPU: 8x Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz
Java Version: 1.7.0_79, Oracle Corporation
Java VM Version: OpenJDK 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 159147272 bytes (151 MB) / 311480320 bytes (297 MB) up to 2134114304 bytes (2035 MB)
JVM Flags: 5 total; -Xmx2G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
Launched Version: 1.8.7
LWJGL: 2.9.4
OpenGL: GeForce GTX 680/PCIe/SSE2 GL version 4.4.0 NVIDIA 331.113, NVIDIA Corporation
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: Yes
Is Modded: Probably not. Jar signature remains and client brand is untouched.
Type: Client (map_client.txt)
Resource Packs: []
Current Language: English (US)
Profiler Position: N/A (disabled)
Linked Issues
is duplicated by1
TRASH-36442
Attachments2
– System Details –
Details:
Minecraft Version: 1.8.7
Operating System: Linux (amd64) version 3.13.0-55-lowlatency
CPU: 8x Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz
Java Version: 1.7.0_79, Oracle Corporation
Java VM Version: OpenJDK 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 159147272 bytes (151 MB) / 311480320 bytes (297 MB) up to 2134114304 bytes (2035 MB)
JVM Flags: 5 total; -Xmx2G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
Launched Version: 1.8.7
LWJGL: 2.9.4
OpenGL: GeForce GTX 680/PCIe/SSE2 GL version 4.4.0 NVIDIA 331.113, NVIDIA Corporation
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: Yes
Is Modded: Probably not. Jar signature remains and client brand is untouched.
Type: Client (map_client.txt)
Resource Packs: []
Current Language: English (US)
Profiler Position: N/A (disabled)Operating System: Linux (amd64) version 3.13.0-55-lowlatency
Java Version: 1.7.0_79, Oracle Corporation
Java VM Version: OpenJDK 64-Bit Server VM (mixed mode), Oracle Corporation
is duplicated by
When ever I load a certain area of my world the attached crash happens.
If the world is started as a server only the client crashes, but the crash report should speak for itself.Steps to reproduce:
1. Download the attached world file
2. Log into this world
3. Look downDescription: Tesselating block in world java.lang.IndexOutOfBoundsException at java.nio.Buffer.checkIndex(Buffer.java:538) at java.nio.DirectByteBuffer.putFloat(DirectByteBuffer.java:887) at bfd.b(SourceFile:414) at bge.a(SourceFile:225) at bgd.a(SourceFile:67) at bht.b(SourceFile:176) at bhp.a(SourceFile:78) at bho.b(SourceFile:121) at bfr.a(SourceFile:842)Note that this crash might be environment dependent.
How the world got corrupted like this
I had the world open to LAN and when I left it Minecraft hung (Which should be covered in a different bug report, when there is any way to reproduce it). After forcing the process to stop and restarting the crash happened when ever joining the world again.Search disclaimer
The only unresolved issue I could find which might be related to this one isMC-81252, but it has a completely different stack trace. There is many other issues about the same/similar crashes but as they are resolved I just assume that they have different causes.How I fixed the corrupted world
To be able to play in this world again, I started it up on a server with render distance 16.
Then I connected with a client on render distance 2 and went so close to the corrupted blocks that they were loaded but didn't get rendered. (An other way to do this is probably to just look in an other direction).
As the crash report tells me which blocks it crashes on (water blocks around 5248,85,2331), I replaced all the blocks the crash happened on with something else:
/fill 5243 64 2331 5272 128 2331 minecraft:stone_slab 0 replace minecraft:water 7
After that I went in the area and no crash happened any more.
To undo the change I replaced all the slabs with water again:
/fill 5243 64 2331 5272 128 2331 minecraft:water 7 replace minecraft:stone_slab 0
is duplicated by
relates to
relates to
When ever I load a certain area of my world the attached crash happens.
If the world is started as a server only the client crashes, but the crash report should speak for itself.Steps to reproduce:
1. Download the attached world file
2. Log into this world
3. Look downDescription: Tesselating block in world java.lang.IndexOutOfBoundsException at java.nio.Buffer.checkIndex(Buffer.java:538) at java.nio.DirectByteBuffer.putFloat(DirectByteBuffer.java:887) at bfd.b(SourceFile:414) at bge.a(SourceFile:225) at bgd.a(SourceFile:67) at bht.b(SourceFile:176) at bhp.a(SourceFile:78) at bho.b(SourceFile:121) at bfr.a(SourceFile:842)Note that this crash might be environment dependent.
How the world got corrupted like this
I had the world open to LAN and when I left it Minecraft hung (Which should be covered in a different bug report, when there is any way to reproduce it). After forcing the process to stop and restarting the crash happened when ever joining the world again.Search disclaimer
The only unresolved issue I could find which might be related to this one isMC-81252, but it has a completely different stack trace. There is many other issues about the same/similar crashes but as they are resolved I just assume that they have different causes.How I fixed the corrupted world
To be able to play in this world again, I started it up on a server with render distance 16.
Then I connected with a client on render distance 2 and went so close to the corrupted blocks that they were loaded but didn't get rendered. (An other way to do this is probably to just look in an other direction).
As the crash report tells me which blocks it crashes on (water blocks around 5248,85,2331), I replaced all the blocks the crash happened on with something else:
/fill 5243 64 2331 5272 128 2331 minecraft:stone_slab 0 replace minecraft:water 7
After that I went in the area and no crash happened any more.
To undo the change I replaced all the slabs with water again:
/fill 5243 64 2331 5272 128 2331 minecraft:water 7 replace minecraft:stone_slab 0When ever I load a certain area of my world the attached crash happens.
If the world is started as a server only the client crashes, but the crash report should speak for itself.Steps to reproduce:
1. Download the attached world file
2. Log into this world
3. Look downDescription: Tesselating block in world java.lang.IndexOutOfBoundsException at java.nio.Buffer.checkIndex(Buffer.java:538) at java.nio.DirectByteBuffer.putFloat(DirectByteBuffer.java:887) at bfd.b(SourceFile:414) at bge.a(SourceFile:225) at bgd.a(SourceFile:67) at bht.b(SourceFile:176) at bhp.a(SourceFile:78) at bho.b(SourceFile:121) at bfr.a(SourceFile:842)Note that this crash might be environment dependent.
How the world got corrupted like this
I had the world open to LAN and when I left it Minecraft hung (MC-72943). After forcing the process to stop and restarting the crash happened when ever joining the world again.Search disclaimer
The only unresolved issue I could find which might be related to this one isMC-81252, but it has a completely different stack trace. There is many other issues about the same/similar crashes but as they are resolved I just assume that they have different causes.How I fixed the corrupted world
To be able to play in this world again, I started it up on a server with render distance 16.
Then I connected with a client on render distance 2 and went so close to the corrupted blocks that they were loaded but didn't get rendered. (An other way to do this is probably to just look in an other direction).
As the crash report tells me which blocks it crashes on (water blocks around 5248,85,2331), I replaced all the blocks the crash happened on with something else:
/fill 5243 64 2331 5272 128 2331 minecraft:stone_slab 0 replace minecraft:water 7
After that I went in the area and no crash happened any more.
To undo the change I replaced all the slabs with water again:
/fill 5243 64 2331 5272 128 2331 minecraft:water 7 replace minecraft:stone_slab 0
relates to
Crash: IndexOutOfBoundsException on Tesselating block in world
When ever I load a certain area of my world the attached crash happens.
If the world is started as a server only the client crashes, but the crash report should speak for itself.Steps to reproduce:
1. Download the attached world file
2. Log into this world
3. Look downDescription: Tesselating block in world java.lang.IndexOutOfBoundsException at java.nio.Buffer.checkIndex(Buffer.java:538) at java.nio.DirectByteBuffer.putFloat(DirectByteBuffer.java:887) at bfd.b(SourceFile:414) at bge.a(SourceFile:225) at bgd.a(SourceFile:67) at bht.b(SourceFile:176) at bhp.a(SourceFile:78) at bho.b(SourceFile:121) at bfr.a(SourceFile:842)Note that this crash might be environment dependent.
How the world got corrupted like this
I had the world open to LAN and when I left it Minecraft hung (MC-72943). After forcing the process to stop and restarting the crash happened when ever joining the world again.Search disclaimer
The only unresolved issue I could find which might be related to this one isMC-81252, but it has a completely different stack trace. There is many other issues about the same/similar crashes but as they are resolved I just assume that they have different causes.How I fixed the corrupted world
To be able to play in this world again, I started it up on a server with render distance 16.
Then I connected with a client on render distance 2 and went so close to the corrupted blocks that they were loaded but didn't get rendered. (An other way to do this is probably to just look in an other direction).
As the crash report tells me which blocks it crashes on (water blocks around 5248,85,2331), I replaced all the blocks the crash happened on with something else:
/fill 5243 64 2331 5272 128 2331 minecraft:stone_slab 0 replace minecraft:water 7
After that I went in the area and no crash happened any more.
To undo the change I replaced all the slabs with water again:
/fill 5243 64 2331 5272 128 2331 minecraft:water 7 replace minecraft:stone_slab 0Note: I reoccurred after that. For now my fix is to avoid having tripwire on top of water. But that is no solution in the long run.
When ever I load a certain area of my world the attached crash happens.
If the world is started as a server only the client crashes, but the crash report should speak for itself.Steps to reproduce:
1. Download the attached world file
2. Log into this world
3. Look downDescription: Tesselating block in world java.lang.IndexOutOfBoundsException at java.nio.Buffer.checkIndex(Buffer.java:538) at java.nio.DirectByteBuffer.putFloat(DirectByteBuffer.java:887) at bfd.b(SourceFile:414) at bge.a(SourceFile:225) at bgd.a(SourceFile:67) at bht.b(SourceFile:176) at bhp.a(SourceFile:78) at bho.b(SourceFile:121) at bfr.a(SourceFile:842)Note that this crash might be environment dependent.
How the world got corrupted like this
I had the world open to LAN and when I left it Minecraft hung (MC-72943). After forcing the process to stop and restarting the crash happened when ever joining the world again.Search disclaimer
The only unresolved issue I could find which might be related to this one isMC-81252, but it has a completely different stack trace. There is many other issues about the same/similar crashes but as they are resolved I just assume that they have different causes.How I fixed the corrupted world
To be able to play in this world again, I started it up on a server with render distance 16.
Then I connected with a client on render distance 2 and went so close to the corrupted blocks that they were loaded but didn't get rendered. (An other way to do this is probably to just look in an other direction).
As the crash report tells me which blocks it crashes on (water blocks around 5248,85,2331), I replaced all the blocks the crash happened on with something else:
/fill 5243 64 2331 5272 128 2331 minecraft:stone_slab 0 replace minecraft:water 7
After that I went in the area and no crash happened any more.
To undo the change I replaced all the slabs with water again:
/fill 5243 64 2331 5272 128 2331 minecraft:water 7 replace minecraft:stone_slab 0Note: It reoccurred after that. For now my fix is to avoid having tripwire on top of water. But that is no solution in the long run.
When ever I load a certain area of my world the attached crash happens.
If the world is started as a server only the client crashes, but the crash report should speak for itself.Steps to reproduce:
1. Download the attached world file
2. Log into this world
3. Look downDescription: Tesselating block in world java.lang.IndexOutOfBoundsException at java.nio.Buffer.checkIndex(Buffer.java:538) at java.nio.DirectByteBuffer.putFloat(DirectByteBuffer.java:887) at bfd.b(SourceFile:414) at bge.a(SourceFile:225) at bgd.a(SourceFile:67) at bht.b(SourceFile:176) at bhp.a(SourceFile:78) at bho.b(SourceFile:121) at bfr.a(SourceFile:842)Note that this crash might be environment dependent.
How the world got corrupted like this
I had the world open to LAN and when I left it Minecraft hung (MC-72943). After forcing the process to stop and restarting the crash happened when ever joining the world again.Search disclaimer
The only unresolved issue I could find which might be related to this one isMC-81252, but it has a completely different stack trace. There is many other issues about the same/similar crashes but as they are resolved I just assume that they have different causes.How I fixed the corrupted world
To be able to play in this world again, I started it up on a server with render distance 16.
Then I connected with a client on render distance 2 and went so close to the corrupted blocks that they were loaded but didn't get rendered. (An other way to do this is probably to just look in an other direction).
As the crash report tells me which blocks it crashes on (water blocks around 5248,85,2331), I replaced all the blocks the crash happened on with something else:
/fill 5243 64 2331 5272 128 2331 minecraft:stone_slab 0 replace minecraft:water 7
After that I went in the area and no crash happened any more.
To undo the change I replaced all the slabs with water again:
/fill 5243 64 2331 5272 128 2331 minecraft:water 7 replace minecraft:stone_slab 0
Note: It reoccurred after that. For now my fix is to avoid having tripwire on top of water. But that is no solution in the long run.When ever I load a certain area of my world the attached crash happens.
If the world is started as a server only the client crashes, but the crash report should speak for itself.Steps to reproduce:
1. Download the attached world file
2. Log into this world
3. Look downDescription: Tesselating block in world java.lang.IndexOutOfBoundsException at java.nio.Buffer.checkIndex(Buffer.java:538) at java.nio.DirectByteBuffer.putFloat(DirectByteBuffer.java:887) at bfd.b(SourceFile:414) at bge.a(SourceFile:225) at bgd.a(SourceFile:67) at bht.b(SourceFile:176) at bhp.a(SourceFile:78) at bho.b(SourceFile:121) at bfr.a(SourceFile:842)Note that this crash might be environment dependent.
How the world got corrupted like this
I had the world open to LAN and when I left it Minecraft hung (MC-72943). After forcing the process to stop and restarting the crash happened when ever joining the world again.Search disclaimer
The only unresolved issue I could find which might be related to this one isMC-81252, but it has a completely different stack trace. There is many other issues about the same/similar crashes but as they are resolved I just assume that they have different causes.Potential Fix
The reason for the exception is that a buffer for rendering overflows.
WorldRenderer.java (in MCP)package net.minecraft.client.renderer; ... public class WorldRenderer { ... private void growBuffer(int p_178983_1_) { LogManager.getLogger().warn("Needed to grow BufferBuilder buffer: Old size " + this.bufferSize * 4 + " bytes, new size " + (this.bufferSize * 4 + p_178983_1_) + " bytes."); this.bufferSize += p_178983_1_ / 4; ByteBuffer var2 = GLAllocation.createDirectByteBuffer(this.bufferSize * 4); this.rawIntBuffer.position(0); var2.asIntBuffer().put(this.rawIntBuffer); this.byteBuffer = var2; this.rawIntBuffer = this.byteBuffer.asIntBuffer(); this.rawFloatBuffer = this.byteBuffer.asFloatBuffer(); } public void setVertexState(WorldRenderer.State p_178993_1_) { this.rawIntBuffer.clear(); // This call causes the crash. Calling growBuffer() when needed fixes the crash for me. this.rawIntBuffer.put(p_178993_1_.func_179013_a()); this.rawBufferIndex = p_178993_1_.getRawBufferIndex(); this.vertexCount = p_178993_1_.getVertexCount(); this.vertexFormat = new VertexFormat(p_178993_1_.func_179016_d()); } ... }Growing the buffer might be the right fix, but it could also be that the reason why it overflows is a bug in the first place.
ProfMobius (Thomas Guimbretiere)is duplicated by
how do I fix it i just tested it and it still does it
i reported my case @ (
MC-93101)
is duplicated by
is duplicated by
@Chris Piggy: This is MC-81738
See MC-81738.
Note: This may be a duplicate of MC-81738 but this one occurred in 1.17.1.
I joined a completely vanilla server on a completely vanilla client and my game crashed "Tesselating block in world":
---- Minecraft Crash Report ---- // Don't be sad, have a hug! <3 Time: 7/8/21, 5:30 PM Description: Tesselating block in world java.lang.NullPointerException: Cannot invoke "eyy.a()" because "☃" is null at eob.a(SourceFile:43) at enz.a(SourceFile:63) at epx$c$b.a(SourceFile:524) at epx$c$b.a(SourceFile:447) at epx$c.k(SourceFile:412) at epx.a(SourceFile:189) at eng.a(SourceFile:918) at eng.a(SourceFile:1142) at enb.a(SourceFile:1026) at enb.a(SourceFile:810) at dvp.f(SourceFile:1112) at dvp.e(SourceFile:728) at net.minecraft.client.main.Main.main(SourceFile:217) A detailed walkthrough of the error, its code path and all known details is as follows: --------------------------------------------------------------------------------------- -- Head -- Thread: Render thread Stacktrace: at eob.a(SourceFile:43) -- Block being tesselated -- Details: Block: Block{minecraft:stone} Block location: World: (80,64,176), Section: (at 0,0,0 in 5,4,11; chunk contains blocks 80,0,176 to 95,255,191), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511) Stacktrace: at enz.a(SourceFile:63) at epx$c$b.a(SourceFile:524) at epx$c$b.a(SourceFile:447) at epx$c.k(SourceFile:412) at epx.a(SourceFile:189) at eng.a(SourceFile:918) at eng.a(SourceFile:1142) at enb.a(SourceFile:1026) -- Affected level -- Details: All players: 1 total; [emm['Crittz33'/79156, l='ClientLevel', x=87.58, y=68.00, z=188.37]] Chunk stats: 961, 625 Level dimension: minecraft:overworld Level spawn location: World: (80,68,192), Section: (at 0,4,0 in 5,4,12; chunk contains blocks 80,0,192 to 95,255,207), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511) Level time: 10705065 game time, 12977268 day time Server brand: vanilla Server type: Non-integrated multiplayer server Stacktrace: at eji.a(SourceFile:370) at dvp.c(SourceFile:2399) at dvp.e(SourceFile:747) at net.minecraft.client.main.Main.main(SourceFile:217) -- Last reload -- Details: Reload number: 1 Reload reason: initial Finished: No Packs: Default, gui_format, Tiny Tweaks -- System Details -- Details: Minecraft Version: 1.17.1 Minecraft Version ID: 1.17.1 Operating System: Windows 10 (amd64) version 10.0 Java Version: 16.0.1, Microsoft Java VM Version: OpenJDK 64-Bit Server VM (mixed mode), Microsoft Memory: 1744737216 bytes (1663 MiB) / 4160749568 bytes (3968 MiB) up to 16106127360 bytes (15360 MiB) CPUs: 12 Processor Vendor: GenuineIntel Processor Name: Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz Identifier: Intel64 Family 6 Model 165 Stepping 2 Microarchitecture: unknown Frequency (GHz): 2.59 Number of physical packages: 1 Number of physical CPUs: 6 Number of logical CPUs: 12 Graphics card #0 name: Intel(R) UHD Graphics Graphics card #0 vendor: Intel Corporation (0x8086) Graphics card #0 VRAM (MB): 1024.00 Graphics card #0 deviceId: 0x9bc4 Graphics card #0 versionInfo: DriverVersion=26.20.100.7642 Graphics card #1 name: NVIDIA GeForce RTX 2060 Graphics card #1 vendor: NVIDIA (0x10de) Graphics card #1 VRAM (MB): 4095.00 Graphics card #1 deviceId: 0x1f15 Graphics card #1 versionInfo: DriverVersion=27.21.14.6677 Memory slot #0 capacity (MB): 8192.00 Memory slot #0 clockSpeed (GHz): 3.20 Memory slot #0 type: DDR4 Memory slot #1 capacity (MB): 8192.00 Memory slot #1 clockSpeed (GHz): 3.20 Memory slot #1 type: DDR4 Virtual memory max (MB): 30884.03 Virtual memory used (MB): 27956.22 Swap memory total (MB): 14679.82 Swap memory used (MB): 1772.05 JVM Flags: 9 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xss1M -Xmx15G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M Launched Version: 1.17.1 Backend library: LWJGL version 3.2.2 build 10 Backend API: NVIDIA GeForce RTX 2060/PCIe/SSE2 GL version 3.2.0 NVIDIA 466.77, NVIDIA Corporation Window size: 1920x1080 GL Caps: Using framebuffer using OpenGL 3.2 GL debug messages: Using VBOs: Yes Is Modded: Probably not. Jar signature remains and client brand is untouched. Type: Client (map_client.txt) Graphics mode: fabulous Resource Packs: vanilla, file/gui_format (incompatible), file/Tiny Tweaks Current Language: English (US) CPU: 12x Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz
![[Mod] ampolive](../../../data/avatars/users/18949.svg){kind=small}
This doesn't seem to be a duplicate of MC-81738, the stack traces are different.
Now also confirmed to crash on Windows thanks to Twitter user @Robitobi01
And Osx is confirmed to crash too thanks to RedstoneSpire
Confirmed.
What's a tesselating block?
"tesselating " is a verb and not a noun. Read that message as IndexOutOfBoundsException on tesselating a block in world
Is the "Open to LAN and minecraft hung" bug
MC-71357? Or are you referring toMC-72943? Or another one?@[Mod] Pokechu22
MC-72943seems to be it. Thank you for linking itCan confirm for 15w31b. See crash_15w31b.txt
I won't attach a crash report for every new version form now on. But I just tested it for 15w33b and 15w33c. Still happens.
Can confirm for 15w35e. I think the issue is just that a buffer needs to be grown.
Confirmed for 15w36d.
Thank you for fixing it!
I wonder whether he found the reason for the buffer overflow.
anyways now the only thing preventing Panda's mushroom cows from being happy in his farm is:
MC-50367I am having a similar issue in 1.10.2 on a server called Arkham Network but it is not repetitive
got the same issue on 1.10.2