PS crashes with encryption option innodb-redo-log-encrypt

/home/mchawla/PS230719_8_0_16_6_debug/bin/mysqld --no-defaults --initialize-insecure --early-plugin-load=keyring_file.so --keyring_file_data=$HOME/PS230719_8_0_16_6_debug/keyring --innodb-redo-log-encrypt
2019-07-23T13:35:08.610505Z 0 [System] [MY-013169] [Server] /home/mchawla/PS230719_8_0_16_6_debug/bin/mysqld (mysqld 8.0.16-6-debug) initializing of server in progress as process 28285
2019-07-23T13:35:53.591069Z 4 [Warning] [MY-010453] [Server] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
2019-07-23T13:36:24.570277Z 0 [System] [MY-013170] [Server] /home/mchawla/PS230719_8_0_16_6_debug/bin/mysqld (mysqld 8.0.16-6-debug) initializing of server has completed

/home/mchawla/PS230719_8_0_16_6_debug/bin/mysqld --core-file --basedir=/home/mchawla/PS230719_8_0_16_6_debug --tmpdir=/home/mchawla/PS230719_8_0_16_6_debug/data --datadir=/home/mchawla/PS230719_8_0_16_6_debug/data --plugin-load-add=tokudb=ha_tokudb.so --tokudb-check-jemalloc=0 --plugin-load-add=rocksdb=ha_rocksdb.so --socket=/home/mchawla/PS230719_8_0_16_6_debug/socket.sock --port=12915 --log-error=/home/mchawla/PS230719_8_0_16_6_debug/log/master.err --server-id=100 --early-plugin-load=keyring_file.so --keyring_file_data=$HOME/PS230719_8_0_16_6_debug/keyring --innodb-redo-log-encrypt 2>&1 &

2019-07-23T13:38:24.480126Z 0 [System] [MY-010116] [Server] /home/mchawla/PS230719_8_0_16_6_debug/bin/mysqld (mysqld 8.0.16-6-debug) starting as process 28347
2019-07-23T13:38:24.628383Z 1 [ERROR] [MY-049008] [InnoDB] [FATAL] Redo log encryption mode can't be switched without stopping the server and recreating the redo logs. Current mode is master_key, requested master_key.
2019-07-23T13:38:24.628408Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: ut0ut.cc:634 thread 139756338353920
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
13:38:24 UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x90af770
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 = 7f1b8ee70c30 thread_stack 0x46000
/home/mchawla/PS230719_8_0_16_6_debug/bin/mysqld(my_print_stacktrace(unsigned char*, unsigned long)+0x43) [0x408314c]
/home/mchawla/PS230719_8_0_16_6_debug/bin/mysqld(handle_fatal_signal+0x291) [0x301c864]
/usr/lib64/libpthread.so.0(+0xf5d0) [0x7f1ba50965d0]
/usr/lib64/libc.so.6(gsignal+0x37) [0x7f1ba31962c7]
/usr/lib64/libc.so.6(abort+0x148) [0x7f1ba31979b8]
/home/mchawla/PS230719_8_0_16_6_debug/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x4576250]
/home/mchawla/PS230719_8_0_16_6_debug/bin/mysqld(ib::fatal::~fatal()+0) [0x457a504]
/home/mchawla/PS230719_8_0_16_6_debug/bin/mysqld(log_read_encryption()+0x443) [0x43ae31f]
/home/mchawla/PS230719_8_0_16_6_debug/bin/mysqld(srv_start(bool, std::string const&)+0x155b) [0x44f142d]
/home/mchawla/PS230719_8_0_16_6_debug/bin/mysqld() [0x425e1e3]
/home/mchawla/PS230719_8_0_16_6_debug/bin/mysqld() [0x426e6ab]
/home/mchawla/PS230719_8_0_16_6_debug/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0x8e) [0x3dd68ea]
/home/mchawla/PS230719_8_0_16_6_debug/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x55f) [0x3fd3cd8]
/home/mchawla/PS230719_8_0_16_6_debug/bin/mysqld() [0x3130d48]
/home/mchawla/PS230719_8_0_16_6_debug/bin/mysqld() [0x416e2e0]
/usr/lib64/libpthread.so.0(+0x7dd5) [0x7f1ba508edd5]
/usr/lib64/libc.so.6(clone+0x6d) [0x7f1ba325e02d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 1
Status: NOT_KILLED
Please help us make Percona Server better by reporting any
bugs at https://bugs.percona.com/
You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.
Writing a core file