aarch64 crash in shutdown under jemalloc after timezone loading

$ podman run --rm --arch arm64  -e LD_PRELOAD="/usr/lib/aarch64-linux-gnu/libjemalloc.so.1" -e MARIADB_ALLOW_EMPTY_ROOT_PASSWORD=1    quay.io/mariadb-foundation/mariadb-devel:10.2

Trying to pull quay.io/mariadb-foundation/mariadb-devel:10.2...

Getting image source signatures

Copying blob aff50928ca0a skipped: already exists  

Copying blob a7d962dca782 skipped: already exists  

Copying blob be039883ad5e skipped: already exists  

Copying blob 379bc4dad914 skipped: already exists  

Copying blob 6857e6f87371 skipped: already exists  

Copying blob a4ce60ef85db skipped: already exists  

Copying blob 34a080d9adc2 skipped: already exists  

Copying blob c44c4b1f68ed skipped: already exists  

Copying blob ff4fc8fe163c skipped: already exists  

Copying blob bd5794e20f9d skipped: already exists  

Copying blob a09d18edeffa skipped: already exists  

Copying blob 4aa5bb43998f skipped: already exists  

Copying blob 7e87d12b725a skipped: already exists  

Copying config cf9e08c6cc done  

Writing manifest to image destination

Storing signatures

2022-03-11 05:47:03+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.2.44+maria~bionic started.

2022-03-11 05:47:06+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'

2022-03-11 05:47:06+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.2.44+maria~bionic started.

2022-03-11 05:47:09+00:00 [Note] [Entrypoint]: Initializing database files

2022-03-11  5:47:11 365136250064 [Warning] InnoDB: Linux Native AIO interface is not supported on this platform. Please check your OS documentation and install appropriate binary of InnoDB.

2022-03-11  5:47:11 365136250064 [Warning] InnoDB: Linux Native AIO disabled.

PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER !

To do so, start the server, then issue the following command:

'/usr/bin/mysql_secure_installation'

which will also give you the option of removing the test

databases and anonymous user created by default.  This is

strongly recommended for production servers.

See the MariaDB Knowledgebase at http://mariadb.com/kb

Please report any problems at http://mariadb.org/jira

The latest information about MariaDB is available at http://mariadb.org/.

Consider joining MariaDB's strong and vibrant community:

https://mariadb.org/get-involved/

2022-03-11 05:47:15+00:00 [Note] [Entrypoint]: Database files initialized

2022-03-11 05:47:16+00:00 [Note] [Entrypoint]: Starting temporary server

2022-03-11 05:47:16+00:00 [Note] [Entrypoint]: Waiting for server startup

2022-03-11  5:47:16 365136250064 [Note] /usr/sbin/mysqld (mysqld 10.2.44-MariaDB-1:10.2.44+maria~bionic) starting as process 229 ...

2022-03-11  5:47:16 365136250064 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2022-03-11  5:47:16 365136250064 [Note] InnoDB: Uses event mutexes

2022-03-11  5:47:16 365136250064 [Note] InnoDB: Compressed tables use zlib 1.2.11

2022-03-11  5:47:16 365136250064 [Note] InnoDB: Using Linux native AIO

2022-03-11  5:47:16 365136250064 [Note] InnoDB: Number of pools: 1

2022-03-11  5:47:16 365136250064 [Note] InnoDB: Using generic crc32 instructions

2022-03-11  5:47:16 365136250064 [Warning] InnoDB: Linux Native AIO interface is not supported on this platform. Please check your OS documentation and install appropriate binary of InnoDB.

2022-03-11  5:47:16 365136250064 [Note] InnoDB: You can disable Linux Native AIO by setting innodb_use_native_aio = 0 in my.cnf

2022-03-11  5:47:16 365136250064 [Warning] InnoDB: Linux Native AIO disabled.

2022-03-11  5:47:16 365136250064 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M

2022-03-11  5:47:16 365136250064 [Note] InnoDB: Completed initialization of buffer pool

2022-03-11  5:47:16 366228570384 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().

2022-03-11  5:47:17 365136250064 [Note] InnoDB: Highest supported file format is Barracuda.

2022-03-11  5:47:17 365136250064 [Note] InnoDB: 128 out of 128 rollback segments are active.

2022-03-11  5:47:17 365136250064 [Note] InnoDB: Creating shared tablespace for temporary tables

2022-03-11  5:47:17 365136250064 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...

2022-03-11  5:47:17 365136250064 [Note] InnoDB: File './ibtmp1' size is now 12 MB.

2022-03-11  5:47:17 365136250064 [Note] InnoDB: 5.7.37 started; log sequence number 1615498

2022-03-11  5:47:17 365136250064 [Note] Plugin 'FEEDBACK' is disabled.

2022-03-11  5:47:17 365136250064 [Warning] 'user' entry 'root@237024c34c54' ignored in --skip-name-resolve mode.

2022-03-11  5:47:17 365136250064 [Warning] 'proxies_priv' entry '@% root@237024c34c54' ignored in --skip-name-resolve mode.

2022-03-11  5:47:17 365136250064 [Note] Reading of all Master_info entries succeeded

2022-03-11  5:47:17 365136250064 [Note] Added new Master_info '' to hash table

2022-03-11  5:47:17 365136250064 [Note] /usr/sbin/mysqld: ready for connections.

Version: '10.2.44-MariaDB-1:10.2.44+maria~bionic'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  mariadb.org binary distribution

2022-03-11 05:47:18+00:00 [Note] [Entrypoint]: Temporary server started.

Warning: Unable to load '/usr/share/zoneinfo/leap-seconds.list' as time zone. Skipping it.

2022-03-11 05:47:36+00:00 [Note] [Entrypoint]: Securing system users (equivalent to running mysql_secure_installation)

2022-03-11 05:47:36+00:00 [Note] [Entrypoint]: Stopping temporary server

220311  5:47:37 [ERROR] mysqld got signal 11 ;

This could be because you hit a bug. It is also possible that this binary

or one of the libraries it was linked against is corrupt, improperly built,

or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help

diagnose the problem, but since we have already crashed, 

something is definitely wrong and this may fail.

Server version: 10.2.44-MariaDB-1:10.2.44+maria~bionic

key_buffer_size=134217728

read_buffer_size=2097152

max_used_connections=1

max_threads=102

thread_count=6

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759920 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0

Attempting backtrace. You can use the following information to find out

where mysqld died. If you see no messages after this, something went

terribly wrong...

stack_bottom = 0x0 thread_stack 0x49000

/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x5500b50304]

The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains

information that should help you find out what is causing the crash.

Writing a core file...

Working directory at /var/lib/mysql