mojira.dev
MC-172787

Crash due to render not found

Not sure what causes it and it is random when it crashes. Sometimes crashes right away, sometimes I can play for hours with no problems.

 

 


Minecraft Crash Report ----
// Don't do that.

Time: 2/20/20 11:47 AM
Description: Manually triggered debug crash

java.lang.Throwable
at dbl.b(SourceFile:454)
at dbn.p(SourceFile:1511)
at dbn.d(SourceFile:964)
at dbn.d(SourceFile:619)
at net.minecraft.client.main.Main.main(SourceFile:204)

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

– Head –
Thread: Render thread
Stacktrace:
at dbl.b(SourceFile:454)

– Affected level –
Details:
All players: 1 total; [dqb['ethanwil'/177, l='MpServer', x=183.83, y=13.98, z=288.37]]
Chunk stats: Client Chunk Cache: 2025, 1521
Level dimension: minecraft:overworld
Level name: MpServer
Level seed: -6047189248555187157
Level generator: ID 01 - flat, ver 0. Features enabled: false
Level generator options: {}
Level spawn location: World: (96,4,240), Chunk: (at 0,0,0 in 6,15; contains blocks 96,0,240 to 111,255,255), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511)
Level time: 1560057 game time, 11649 day time
Known server brands:
Level was modded: false
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
Server brand: vanilla
Server type: Integrated singleplayer server
Stacktrace:
at dno.a(SourceFile:450)
at dbn.c(SourceFile:1921)
at dbn.d(SourceFile:634)
at net.minecraft.client.main.Main.main(SourceFile:204)

– System Details –
Details:
Minecraft Version: 1.15.2
Minecraft Version ID: 1.15.2
Operating System: Windows 10 (amd64) version 10.0
Java Version: 1.8.0_51, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 731594744 bytes (697 MB) / 1845493760 bytes (1760 MB) up to 2147483648 bytes (2048 MB)
CPUs: 16
JVM Flags: 9 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xss1M -Xmx2G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M
Launched Version: 1.15.2
Backend library: LWJGL version 3.2.2 build 10
Backend API: GeForce RTX 2070/PCIe/SSE2 GL version 4.6.0 NVIDIA 442.19, NVIDIA Corporation
GL Caps: Using framebuffer using OpenGL 3.0
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)
CPU: 16x AMD Ryzen 7 2700 Eight-Core Processor

Comments 3

Can you attach the launcher_log found in /.minecraft after the game crashes?

Not a mod, but I looked at your post: "Description: Manually triggered debug crash". If you're using F3 + C to get your coordinates (or just pressing it for some other reason), holding it for 10 seconds causes an (intentional) crash according to the MC wiki. If not, you've found a very weird bug!

It's most likely they intended to cause a debug crash, as to give us some basic information regarding their system/game

Ethan Wilson

(Unassigned)

Unconfirmed

(Unassigned)

1.15.2, 20w08a

Retrieved