I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en

which is also acted as an empty guard for destroy and should be set after new.

This ubsan can be reproduced using the following SQL along with this pr #7179

SET max_memory_usage = 1000000000;
SELECT
    number,
    argMax(number, tuple(toFixedString('1234567890123456789012', 25)))
FROM numbers(100000000);

Why did CI not catch this? Because it only happens when the memory exception is thrown right after a field is created (note the string size, <=22 is fine), which is very unlikely.

Category (leave one):

• Bug Fix