Terrible performance with large forest fires
Environment
OS: Windows 10, Java 1.8.0_51 64bit
CPU: Intel Core i7-4770k
GPU: GTX 960 4G
RAM: 16GB
Linked Issues
is duplicated by6
relates to6
- Fixed
[Mod] markderickson
MyFullName
- 53
- 23
- Confirmed
Very Important
- Performance
- block-update fire forest lighting
1.13.2 - 21w40a
1.13.2 19w14b 1.14-pre2 1.14-pre3 1.14-pre4 1.14-pre5 1.14 1.14.1 1.14.2-pre1 1.14.2-pre2 1.14.2 1.14.3 1.14.4-pre1 1.14.4-pre3 1.14.4-pre4 1.14.4-pre5 1.14.4-pre6 1.14.4 19w34a 19w35a 19w36a 19w37a 19w38b 19w39a 19w40a 19w41a 19w42a 19w45b 19w46b 1.15-pre1 1.15-pre2 1.15-pre3 1.15-pre4 1.15-pre5 1.15-pre6 1.15-pre7 1.15 1.15.1 1.15.1-pre1 1.15.2-pre1 1.15.2-pre2 1.15.2 20w06a 20w07a 20w08a 20w09a 20w10a 20w11a 20w12a 20w13a 20w13b 20w15a 20w17a 20w18a 20w19a 20w20a 20w20b 20w21a 1.16-pre2 1.16-pre3 1.16-pre5 1.16-rc1 1.16 1.16.1 20w27a 20w28a 20w29a 20w30a 1.16.2-pre1 1.16.2-rc1 1.16.2-rc2 1.16.2 1.16.3-rc1 1.16.3 1.16.4-pre1 1.16.4-pre2 1.16.4-rc1 1.16.4 20w45a 20w46a 20w48a 20w49a 20w51a 21w03a 1.16.5 21w05a 21w05b 21w06a 21w07a 21w08b 21w10a 21w11a 21w13a 21w14a 21w19a 1.17-pre2 1.17.1 21w39a 21w40a- 19w45a
Created Issue:
Terrible performance
Windows 10, Java 1.8.0_51 64bit
cpu i7-4770k
gpu GTX 960 4G
ram 16GB
Environment
Performance of minecraft is bad, it is known issue for a long time, but this is absolutelly unplayable. The lags I am experiencing and quite good computer is something extreme. The gameplay is not smooth while playing normal survival, but things become absolutely terrible when player wants to use fire. When using flint and steel for deforestation, the game performance dives to the bottom of the oceans. It runs at 1 frame per second, which is absolutelly unplayable.
- Unresolved
- Open
- Unconfirmed
- 3 - Normal
- 19w14b
Windows 10, Java 1.8.0_51 64bit
cpu i7-4770k
gpu GTX 960 4G
ram 16GB
Performance of Minecraft is bad, it is known issue for a long time, but this is absolutely unplayable. The lags I am experiencing and quite good computer is something extreme. The gameplay is not smooth while playing normal survival, but things become absolutely terrible when player wants to use fire. When using flint and steel for deforestation, the game performance dives to the bottom of the oceans. It runs at 1 frame per second, which is absolutely unplayable.
Performance of minecraft is bad, it is known issue for a long time, but this is absolutelly unplayable. The lags I am experiencing and quite good computer is something extreme. The gameplay is not smooth while playing normal survival, but things become absolutely terrible when player wants to use fire. When using flint and steel for deforestation, the game performance dives to the bottom of the oceans. It runs at 1 frame per second, which is absolutelly unplayable.
Windows 10, Java 1.8.0_51 64bit
cpu i7-4770k
gpu GTX 960 4G
ram 16GB
From the screenshot I can see that you lighted a big forest on fire, that would cause a lot of lighting updates + block updates which might cause lag
Terrible performance with large forest fires
Performance of Minecraft is bad, it is known issue for a long time, but this is absolutely unplayable. The lags I am experiencing and quite good computer is something extreme. The gameplay is not smooth while playing normal survival, but things become absolutely terrible when player wants to use fire. When using flint and steel for deforestation, the game performance dives to the bottom of the oceans. It runs at 1 frame per second, which is absolutely unplayable.
is duplicated by
is duplicated by
is duplicated by
relates to
is duplicated by
relates to
relates to
relates to
is duplicated by
@slicedlime Just wanted to add some screenshots on a different system setup.
Biome blend= 3x3 on both versions.
Just to clarify, these are not very trustworthy because at some point being a block or two nearer the fire provokes a HUGE performance drop. I can elaborate more on this if needed.
Windows 10, Java 1.8.0_51 64bit
cpu i7-4770k
gpu GTX 960 4G
ram 16GB
OS: Windows 10, Java 1.8.0_51 64bit
CPU: Intel Core i7-4770k
GPU: GTX 960 4G
RAM: 16GB
relates to
is cloned by
Duplicate of MC-147548
Duplicate of MC-147548
Duplicate of MC-147548
Thank you for your report!
We're actually already tracking this issue in MC-147548, so I resolved and linked this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
We will need some more information to diagnose the performance issues. In game, please do the following:
while the lag is occurring, run:
/debug start
wait a bit of time
/debug stopAlso, run:
/debug report
After which, attach the result files found in your /debug folder inside the .minecraft directory to this report. Unfortunately, these commands were only introduced after 1.13, but the reports will assist in diagnosing your issue.
I do want to point out though that "My FPS and TPS are lower" isn't sufficient to be a helpful bug report. It is no secret that over time, as more features have been added to the game, that there have been performance degradation. There have been similar reports in the past for bad performance, but as of 1.15 the developers have requested that reports identify specific causes for performance issues (e.g. "Lots of entities in a small space"). Furthermore, if multiple causes are identified, we would want to keep these in separate reports for better tracking.
Examples of such reports include: MC-147548, MC-164123, MC-166005, MC-123584
As of 1.15, the developers have requested that bug reports regarding performance be specific to better address problems. Saying you have "bad performance" in a bug report does not magically tell the developers what the problem is, nor how to fix it. If you are able to identify a specific problem regarding performance, feel free to make a new report about that issue. Here are some examples of suck tickets: MC-147548 MC-166005
Clones MC-147548.








I'm afraid this is not a bug, this is lag due to a lot of fire needing to be processed on your PC, just like igniting a ton of TNT at the same time.
I can confirm this for 1.14-pre1, and 1.13.2 as well - 1.12.2 performs much smoother when there is a large fire. Added two screenshots, one on 1.14-pre1 on a Buffet Dark Forest set on fire, the other one 1.12.2 with a customised Dark Forest only world set on fire, With the F3-Shift screen turned on, going down to the thing that seems to cause the most lag (root.gameRenderer.level.terrain_setup.rebuildNear).
Edit: I do realise that my 1.14 is running on Java 12 (running quite well actually) - I also tested it on the bundled Java with the same result.
Still in all 1.14 Pre-Releases
Still in 1.14 Release
It was easier to have a tree lit on fire and have the game run smoothly pre-1.14. Now it lags too much.
Still in 1.14.1 Release
Still in 1.14.2 Pre-Release 1 and 1.14.2 Pre-Release 2
Still in 1.14.3 Pre-Release 2.
Still in 19w45a and 19w45b.
What is your biome blend setting?
@slicedlime The biome blend is at its default setting (5x5).
Thanks. Could you post another screenshot like the previous one - with the performance graph, on 19w46a or later please?
@slicedlime Here there are!

@slicedlime Just wanted to add some screenshots on a different system setup.
Biome blend= 3x3 on both versions.
Just to clarify, these are not very trustworthy because at some point being a block or two nearer the fire provokes a HUGE performance drop. I can elaborate more on this if needed.
Affects 20w12a
Affects 1.16 pre release 2
Can confirm for 1.16 pre release 5
still happens in 20w27a
Reporter changed to [Mod] markderickson upon request in Discord, since the original reporter has been inactive.
Why did you light this poor forest on fire in the first place?
It might not be caused by purposely lighting it on fire, it could also be caused by a lava lake.
Can confirm in 1.17.1. Doesn't even need to be a large forest; a few burning trees are enough to cause frame rate issues.
That's worse in 21w39a
Can confirm in 21w40a.
This issue was fixed, but keeps being reopened. The amount of lag has been reduced by a drastic amount to when this was first introduced. This one must stay closed.
I have created a new ticket for the post-19w45a issue: MC-240450.