"Creating buffer: Invalid enumerated parameter value" spammed in log
The bug
When I enter certain areas, the following error message is spammed in the game output:
csr Sound engine error Creating buffer: Invalid enumerated parameter value.
Steps to reproduce
- Download the attached world MC-147099.zip

- Teleport to the following location
/execute in minecraft:overworld run tp @s -58.51 87.00 -114.80 29.79 19.85
→ Notice the error messages in the log
I also attached my sound settings, just in case that plays a role in this. My render distance is 10 chunks.
Created Issue:
"Creating buffer: Invalid enumerated parameter value" spammed in log
The bug
When I enter certain areas, the following error message is spammed in the game output:
csr Sound engine error Creating buffer: Invalid enumerated parameter value.Steps to reproduce
- Download the attached world MC-147099.zip
- Teleport to the following location
/execute in minecraft:overworld run tp @s -58.51 87.00 -114.80 29.79 19.85→ Notice the error messages in the log
Changed Description:
The bug
When I enter certain areas, the following error message is spammed in the game output:
csr Sound engine error Creating buffer: Invalid enumerated parameter value.Steps to reproduce
- Download the attached world MC-147099.zip
- Teleport to the following location
/execute in minecraft:overworld run tp @s -58.51 87.00 -114.80 29.79 19.85→ Notice the error messages in the log
I also attached my sound settings, just in case that plays a role in this. My render distance is 10 chunks.
Added Attachments:
Added Assignee:
[Mojang] Bartosz Bok

Just out of curiosity, how did you get ender dragon at position [NaN, NaN, Nan] !?
Huh.. I didn't notice that. I guess that happened while I was trying to reproduce
MC-146316, which seems to be the root of the problem here.Running "/summon ender_dragon" will spawn the dragon, then teleport it to the world origin (0, 0, 0) (or sometimes NaN?, also see
MC-147152). After teleporting there myself, I receive the following error messages:I guess this explains why I received the error messages when loading chunks around (0, 0, 0) in the attached world.
Seems to be fixed in 19w14a. The attached world no longer produces the issue, nor does spawning the ender dragon using /summon.