Zailer43

> Can you show a profile the data that supports this assessment? Thanks.
 
I have made a small benchmark with 100 million iterations and 5 cycles of iterations, the result I got was:

Current implementation: 1799595435ns (1799ms)
Current implementation: 1176125877ns (1176ms)
Current implementation: 1143411915ns (1143ms)
Current implementation: 1124996127ns (1124ms)
Current implementation: 1160581816ns (1160ms)
Simplified implementation: 421642052ns (421ms)
Simplified implementation: 137799694ns (137ms)
Simplified implementation: 178195836ns (178ms)
Simplified implementation: 167903541ns (167ms)
Simplified implementation: 182431767ns (182ms)

code:

java
public class Test {
    private static final int ITERATIONS = 100000000;
    private static final int ITERATIONS_CYCLES = 5;

    public static void main(String[] args) {
        for (int j = 0; j < ITERATIONS_CYCLES; j++) {
            long start = System.nanoTime();
            for (int i = 0; i < ITERATIONS; i++) {
                char c = (char) (i % 128);
                Character.toString(c).toLowerCase(Locale.ROOT).charAt(0);
            }
            long end = System.nanoTime();
            long currentTime = end - start;
            System.out.println("Current implementation: " + currentTime + "ns (" + TimeUnit.NANOSECONDS.toMillis(currentTime) + "ms)");
        }

        for (int j = 0; j < ITERATIONS_CYCLES; j++) {
            long start = System.nanoTime();
            for (int i = 0; i < ITERATIONS; i++) {
                char c = (char) (i % 128);
                Character.toLowerCase(c);
            }
            long end = System.nanoTime();
            long simplifiedTime = end - start;
            System.out.println("Simplified implementation: " + simplifiedTime + "ns (" + TimeUnit.NANOSECONDS.toMillis(simplifiedTime) + "ms)");
        }
    }
}

Can confirm in 1.19.3

If you look at the logs a few seconds before it said "crash" this had occurred

ready, I already uploaded the launcher_log.txt, although with sublime text I replaced all the times that my username appears in the paths of the pc

Can confirm in 1.17.1

Can confirm in 1.17.1

Confirmed for 1.17

I can't reproduce this with /summon either but with an item with EntityTag yes

Can confirm in 1.17

Yes, but in the case of simply putting the integer it accepts it as if I put it as a string

In the following case it gives me an item that when I put it there are 3 candles but they are off

/give @s candle{BlockStateTag:{candles:3,lit:true}}

I've already checked it and it's not a driver's problem as indicated in that problem, plus the one quoted from the driver is not compatible with my PC

I did not realize that it does not leave more than 10 mb

It happens to me in survival and creative and that's when I don't look at blocks

I got the error in 1.15

crash report: