Bug #99356 Mysql is in restart loop (can't start)

Description:
information that should help you find out what is causing the crash.
2020-04-26T03:53:20.861878Z 0 [Warning] [MY-010101] [Server] Insecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.
2020-04-26T03:53:20.861955Z 0 [System] [MY-010116] [Server] /usr/local/mysql/bin/mysqld (mysqld 8.0.19) starting as process 8196
2020-04-26T03:53:20.863770Z 0 [Warning] [MY-010159] [Server] Setting lower_case_table_names=2 because file system for /usr/local/mysql/data/ is case insensitive
2020-04-26T03:53:21.708107Z 0 [System] [MY-010229] [Server] Starting XA crash recovery...
2020-04-26T03:53:21.716258Z 0 [System] [MY-010232] [Server] XA crash recovery finished.
2020-04-26T03:53:21.729783Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2020-04-26T03:53:21.732495Z 0 [Warning] [MY-011810] [Server] Insecure configuration for --pid-file: Location '/usr/local/mysql/data' in the path is accessible to all OS users. Consider choosing a different directory.
2020-04-26T03:53:21.746501Z 0 [System] [MY-010931] [Server] /usr/local/mysql/bin/mysqld: ready for connections. Version: '8.0.19'  socket: '/tmp/mysql.sock'  port: 3306  MySQL Community Server - GPL.
2020-04-26T03:53:21.951539Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: '/tmp/mysqlx.sock' bind-address: '::' port: 33060
2020-04-26T03:53:22.729508Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: dict0dict.cc:3338:for_table || ref_table thread 123145448841216
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.
03:53:22 UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x7f9c18311c00
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 = 700008bbdeb0 thread_stack 0x46000
0   mysqld                              0x000000010a483ffc my_print_stacktrace(unsigned char const*, unsigned long) + 60
1   mysqld                              0x000000010988c3d9 handle_fatal_signal + 425
2   libsystem_platform.dylib            0x00007fff7101242d _sigtramp + 29
3   ???                                 0x000000010e397bcb 0x0 + 4533615563
4   libsystem_c.dylib                   0x00007fff70ee7a1c abort + 120
5   mysqld                              0x000000010ab7afd4 ut_dbg_assertion_failed(char const*, char const*, unsigned long) (.cold.1) + 84
6   mysqld                              0x000000010a85c051 ut_dbg_assertion_failed(char const*, char const*, unsigned long) + 273
7   mysqld                              0x000000010a5d80a2 dict_foreign_add_to_cache(dict_foreign_t*, char const**, bool, bool, dict_err_ignore_t) + 1714
8   mysqld                              0x000000010a5ec3c4 dd_table_load_fk_from_dd(dict_table_t*, dd::Table const*, char const**, dict_err_ignore_t, bool) + 1572
9   mysqld                              0x000000010a5f210a dict_table_t* dd_open_table_one<dd::Table>(dd::cache::Dictionary_client*, TABLE const*, char const*, dd::Table const*, THD*, std::__1::deque<char const*, ut_allocator<char const*> >&) + 7098
10  mysqld                              0x000000010a5e2614 dd_table_open_on_dd_obj(dd::cache::Dictionary_client*, dd::Table const&, dd::Partition const*, char const*, dict_table_t*&, THD*) + 2196
11  mysqld                              0x000000010a5e3d43 dd_table_open_on_id_low(THD*, MDL_ticket**, unsigned long long) + 2019
12  mysqld                              0x000000010a5e31f5 dd_table_open_on_id(unsigned long long, THD*, MDL_ticket**, bool, bool) + 2437
13  mysqld                              0x000000010a7df0cb row_purge_step(que_thr_t*) + 763
14  mysqld                              0x000000010a798047 que_run_threads(que_thr_t*) + 375
15  mysqld                              0x000000010a811125 srv_worker_thread() + 677
16  mysqld                              0x000000010a823017 void Runnable::operator()<void (*)()>(void (*&&)()) + 199
17  mysqld                              0x000000010a822e94 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, Runnable, void (*)()> >(void*) + 52
18  libsystem_pthread.dylib             0x00007fff7101de65 _pthread_start + 148
19  libsystem_pthread.dylib             0x00007fff7101983b thread_start + 15

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): 
Connection ID (thread ID): 0
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

How to repeat:
I don't know. It is happening for the third time. In last two occurrences I was forced to get into force_recovery mode and backup the database and then install a new mysql server and restore the database.

Thank you for the bug report. We need a repeatable test case anyway, check similar issue: https://bugs.mysql.com/bug.php?id=97310.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".