The game’s render thread capacity limit can reached causing the limit will then be increased by a factor of 2 continually until the thread is too big and too full. This will cause rendering issues, lag, and even crashes.
Steps to Reproduce:
(It is unclear to me if this is the only way, however it is how I found myself experiencing the issue)
To observe this issue better, inside of the launcher enable the debug output log.
Open one instance of the game
Join a world
Set a high render distance (say, 20)
Allow all the chunks to render
Repeat steps 1-4 with a new instance of the game, keeping the previous open.
Observed & Expected:
You will notice in the log that the following error is output in both instances:
14:57:40.492
gxa
Render thread
Resizing Dynamic Transforms UBO, capacity limit of 8 reached during a single frame. New capacity will be 16.14:57:40.517
gxa
Render thread
Resizing Dynamic Transforms UBO, capacity limit of 16 reached during a single frame. New capacity will be 32.… and so on until:
14:58:02.701
gxa
Render thread
Resizing Dynamic Transforms UBO, capacity limit of 2048 reached during a single frame. New capacity will be 4096.On the second instance of the game after the upper limit of 4096 is reached, you may see rendering issues start to occur, or even a crash with exit code -1073741819.
The error output to the log I saw when the upper limit was reached was this:
14:38:35.338
fmd
Thread-8
OpenGL debug message: id=1014, source=API, type=ERROR, severity=HIGH, message='No detailed debug message due to a non-debug context'‘fmd’ was not always consistent (sometimes a different 3 letter combination), and so wasn’t the thread number.
Rendering Issues:
[media][media][media][media]Environment
RDNA 2:
• AMD Radeon RX 6600, Driver Version 25.6.1
• AMD Radeon RX 6600 XT, Driver Version 25.5.1
• AMD Radeon Graphics = AMD Radeon 680M (AMD Ryzen 9 6900HX), Driver Version 24.10.24 ❓
• AMD Radeon Graphics (AMD Ryzen 7 7800X3D), Driver Version 24.9.1
RDNA 3:
• AMD Radeon RX 7600, Driver Version 25.6.1
• AMD Radeon RX 7600 XT
• AMD Radeon RX 7700 XT, Driver Version 24.10.24 ❓
• AMD Radeon Graphics = AMD Radeon 760M (AMD Ryzen 5 8600G)
Linked issues
is duplicated by 9
MC-297773
Sky Flickering Black and Normal
Resolved
MC-297426
Crash when rendering water in latest snapshot
Resolved
MC-298383
The sky flickers when a menu is open
Resolved
MC-298801
The sky flickers
Resolved
MC-298938
The sky flickers from day to night even during daytime, or it stays as night in the day
Resolved
Attachments
Comments 11
@Nathan Adams Unfortunately I am unable to reproduce the issue again due to not knowing exactly how it originally occurred, despite my testing again. I can’t provide an F3 screenshot while it occurs, however here is one without the sky flickering occurring at the time if that’s still of any value:
[media]I tried relaunching the game numerous times to reproduce the bug again, and in some instances would have this error spammed in the console, also getting a crash with error code -1073741819 a few times. I’m unsure if these are related or not.
10:10:38.140
fma
Thread-10
OpenGL debug message: id=1014, source=API, type=ERROR, severity=HIGH, message='No detailed debug message due to a non-debug context'
I will try testing again when I can, however I am going out of town for the next few days and this was the best additional context I could provide with my limited time.
I am also experiencing this error (the same output as described above with exit code -1073741819). It usually occurs when opening a world for the first time after starting the game. Since the snapshot in which the chunk range of the clouds can be changed. I can see that when I open a world for the first time after starting the game, the edges of the picture become darker. This was not the case before. Maybe this information will help. Hardware should not be the problem. GPU with 16 gb an 7900 x3d.
Affects 1.21.6 Pre-Release 4.
The Resizing Transforms UBO... also appears on NVIDIA graphics cards. It can also exceed the capacity limit by more than 16000.
The error seems to have more to do with the Open GL debug message 1014. This is always spammed with every game tick after entering a world when graphics errors or a crash occur. Maybe this is helpful for the developers.
This issue seems to have gotten significantly worse recently, whether that be due to Minecraft or AMD drivers.
Starting from snapshot 25w16a all the way up to 1.21.6, I am totally incapable of launching the game past the panorama loading.
My JVM arguments and Java version have all been reset to default, but that did not fix the issue.
Once loading into the panorama, my game crashes after a few seconds with error code -1073741819.
Here is a video demonstration of this occurring in 1.21.6:
[media]This is with:
GPU: RX 6600xt
CPU: Ryzen 5 5600X
I can launch and play version 1.21.6 just fine. AMD Radeon RX 570 Series, Driver Version 25.5.1.250226 (as per the F3 debug menu in-game). CPU: 28x Intel(R) Core(TM) i7-14700K.
Can I please have a screenshot of the F3 screen?