In my log files, these messages keep showing up:
[01:23:40] [Chunk Renderer 0/WARN]: Needed to grow BufferBuilder buffer: Old size 524288 bytes, new size 2621440 bytes.
[01:23:51] [Client thread/WARN]: Unable to play unknown soundEvent: minecraft:none
[01:23:54] [Chunk Renderer 0/WARN]: Needed to grow BufferBuilder buffer: Old size 524288 bytes, new size 2621440 bytes.
[01:23:57] [Chunk Renderer 0/WARN]: Needed to grow BufferBuilder buffer: Old size 524288 bytes, new size 2621440 bytes.
[01:23:59] [Client thread/WARN]: Unable to play unknown soundEvent: minecraft:none
[01:24:01] [Chunk Renderer 0/WARN]: Needed to grow BufferBuilder buffer: Old size 524288 bytes, new size 2621440 bytes.
[01:24:15] [Client thread/WARN]: Unable to play unknown soundEvent: minecraft:none
[01:24:21] [Client thread/WARN]: Unable to play unknown soundEvent: minecraft:none
[01:24:24] [Chunk Renderer 1/WARN]: Needed to grow BufferBuilder buffer: Old size 524288 bytes, new size 2621440 bytes.
[01:24:28] [Client thread/WARN]: Unable to play unknown soundEvent: minecraft:none
[01:25:30] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 2104ms behind, skipping 42 tick(s)
Linked issues
is duplicated by 2
Comments 13
Looks like these are only warnings, not errors. While it is unusual for these messages to show up, it appears that the game is detecting a potential issue (buffer too small) and resolving it (growing the buffer), so overall there is no problem.
Do you have your view distance set to a very high value, such as 15 or higher? Do the messages stop if you lower your view distance?
reopen this is not intended anyone who says otherwise should be terminated. buffers are FIXED in size. it might say 'WARN' but it is a error it is telling you the buffer is too small. why you think you still have chunk problems still...
@Sycholic, as indicated by the report:
[Mojang] Mog (Ryan Holtz) made changes - 17/Jul/14 1:27 PM
Field Original Value New Value
Status Open [ 1 ] Resolved [ 5 ]
Resolution Works As Intended [ 6 ]
Since a dev resolved it, it is intended. While a buffer may be fixed in size, what I imagine is occurring here is that a new buffer with a larger size is created, and data is transferred over as needed.
hard to know because there is too many variables to content with since Java runtime args (let alone ingame graphics options like VBO etc) are not static for MC, nor is this saying what thread this is coming from. I could do some testing but I will go and say this. this error and massive visual glitching both have appeared the same time.. (14w snaps and since there after...) simple as that. you should not get warnings that your 'fixed' buffer memory is being resized if it was correct in the first place...
it is not a warning because it is intended... I only bring this up because it STILL exists (let alone the massive visual glitching) even in 15w39b
The visual glitching was fixed for me by using Fancy graphics (ew, but I use a texture pack with very little leaf transparency to make it not so horrible). Yes, it's laggier, but Optifine fixes this in the 1.8 versions (the visual glitching, anyways) and in 1.9 snapshots I easily get ~80 FPS with everything set as high/slow/fancy as it goes except render distance (I hate having a huge render distance if I really don't need it, so I stick with 3 anyways).
So how is this fixed? My son is losing his mind over this error for the past 6 months. I have uninstalled Java and reinstalled it, same with MC, and after 2 minutes "Java SE binary has stopped working" shows up and then the game goes to the log saying" needed to grow bufferbuild buffer". I seen this all over the internet, but no one knows how to fix it.
Comment of @unknown on reddit
Nothing wrong here.
It's should be a debug statement not warning.
It is just saying it has to allocate bigger buffers. Some versions ago we had some issues with stubborn buffers that refused to grow. The messages you see were added for debugging.
It should all work fine now 🙂
You can trigger it yourself be making a 16x16x16 area in 1 chunk section from fences or slime blocks 🙂
Eh... WHY does this work as intended?