mysqldump of triggers cause killing of processes by OOM- Killer

We have been observing lately an increase of the value of the global variable memory_used during execution of a full mysqldump. The value of this variable can go up to a value between 1.5Gb and 2Gb.
After doing some investigation we could see that it occurs when the triggers are included in the dump. When they are not included or if they are none it does not occur. Currently we databases with 500 triggers defined in several schemas. It does not look like a memory leak as once the additional memory is allocated running another dump does increase the size of memory_used.
Doing some research we find the following issue that seems similar to our problem but related to stored procedures MDEV-20699. Does the "show create trigger" has the same behaviour as "show create procedure " and would be allocating caches memory even if they are not executed? Otherwise, how can we identify what is increasing the memory_used allocation.