Setting and changing data of signs creates unnecessary "extra" tags and causes slow downs
The bug
After playing around with some toggle-text signs I found the game would drop from 300+ fps down to around 10 after a few toggles, which seemed very odd. Looking away from the sign would return the fps back up high. Believe it has something to do with extra extra: [] tags appearing.
Running data merge block <pos> on a sign will add an extra: [] to each Text part of a sign. This effect also seems to stack. See images below. First is the initial sign data. Then I add an empty text, then I have done it 3 more times.
Linked Issues
is duplicated by3
Created Issue:
Changing data of Sign blocks causes slow downs
After playing around with some toggle-text signs I found the game would drop from 300+ fps down to around 10 after a few toggles, which seemed very odd. Looking away from the sign would return the fps back up high. Found it is due to how data seems to be merged with the block.
Running data merge block <pos> on a sign will add an extra: [] to each Text part of a sign. This effect also stacks. See images below. First is the initial sign data. Then I add an empty text, then I have done it 3 more times.
After playing around with some toggle-text signs I found the game would drop from 300+ fps down to around 10 after a few toggles, which seemed very odd. Looking away from the sign would return the fps back up high.
Found it is due to how data seems to be merged with the block.Running data merge block <pos> on a sign will add an extra: [] to each Text part of a sign. This effect also stack
s. See images below. First is the initial sign data. Then I add an empty text, then I have done it 3 more times.After playing around with some toggle-text signs I found the game would drop from 300+ fps down to around 10 after a few toggles, which seemed very odd. Looking away from the sign would return the fps back up high. Believe it has something to do with extra extra: [] tags appearing.
Running data merge block <pos> on a sign will add an extra: [] to each Text part of a sign. This effect also seems to stack. See images below. First is the initial sign data. Then I add an empty text, then I have done it 3 more times.
relates to
Changing data ofSign blocks causes slow downsChanging data of sign blocks causes slow downs
Changing data of signblockscauses slow downsChanging data of signs creates unnecessary "extra" tags and causes slow downs
is duplicated by
The bug
After playing around with some toggle-text signs I found the game would drop from 300+ fps down to around 10 after a few toggles, which seemed very odd. Looking away from the sign would return the fps back up high. Believe it has something to do with extra extra: [] tags appearing.
Running data merge block <pos> on a sign will add an extra: [] to each Text part of a sign. This effect also seems to stack. See images below. First is the initial sign data. Then I add an empty text, then I have done it 3 more times.
is duplicated by
Changing data of signs creates unnecessary "extra" tags and causes slow downsSetting and changing data of signs creates unnecessary "extra" tags and causes slow downs
is duplicated by
Duplicate of MC-131019 propably, because the unnecessary "extra" tags are the cause for the high CPU and memory usage.
This issue seems to be duplicate of few others:
- Initial report - client (stack overflow): fixed via
MC-121331 - Initial report - server (watchdog) - server seems to writing logs about overload (`Can't keep up!`), so maybe some IO contention? Does not seem related directly to this
- Later reproductions seem to be duplicates of
MC-45838 MC-130303is symptom ofMC-131019and seems not related to this one




I can confirm that the "extra: [] tags" can cause extreme lag. They are created not only by data merge, but also by copying them with "pick block", or by the clone command, or structure save / load.
This is especially bad for map makers, a map with only a few copied signs is unplayable.
The picture shows a sign before and after it was copied with "pick block".

Affects 1.13-pre2
Affects 1.13-pre3
Affects 1.13-pre4
Confirmed for 1.13-pre5 but for me the lag keep going even when I can't see the sign (by looking up for example)