Bug #115720 Signal SIGSEGV (Invalid permissions for mapped object) at address 0x538
Submitted: 29 Jul 2024 16:34 Modified: 30 Jul 2024 21:51
Reporter: Brian Webster Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:8.4.1_0 OS:MacOS
Assigned to: CPU Architecture:ARM

[29 Jul 2024 16:34] Brian Webster
Description:
MySQL Server doesn't start with large amount of databases. Here is what's in the log file:

2024-07-29T15:54:09.960602Z 0 [System] [MY-015015] [Server] MySQL Server - start.
2024-07-29T15:54:10.096586Z 0 [System] [MY-010116] [Server] /opt/local/lib/mysql8/bin/mysqld (mysqld 8.4.1) starting as process 57940
2024-07-29T15:54:10.097257Z 0 [Warning] [MY-010159] [Server] Setting lower_case_table_names=2 because file system for /opt/local/var/db/mysql8/ is case insensitive
2024-07-29T15:54:10.100990Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-07-29T15:54:10.440568Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2024-07-29T15:54:10Z UTC - mysqld got signal 11 ;
Signal SIGSEGV (Invalid permissions for mapped object) at address 0x538
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
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 = 0 thread_stack 0x100000
0   mysqld                              0x0000000105564a68 my_print_stacktrace(unsigned char const*, unsigned long) + 68
1   mysqld                              0x0000000104acc5fc print_fatal_signal(int, __siginfo*) + 952
2   mysqld                              0x0000000104acc1e8 handle_fatal_signal(int, __siginfo*, void*) + 144
3   libsystem_platform.dylib            0x00000001987af584 _sigtramp + 56
4   mysqld                              0x000000010571fcd0 Validate_files::check(std::__1::__wrap_iter<dd::Tablespace const* const*> const&, std::__1::__wrap_iter<dd::Tablespace const* const*> const&, unsigned long) + 2440
5   mysqld                              0x000000010574ea1c void Detached_thread::operator()<std::__1::function<void (std::__1::__wrap_iter<dd::Tablespace const* const*> const&, std::__1::__wrap_iter<dd::Tablespace const* const*> const&, unsigned long)>, std::__1::__wrap_iter<dd::Tablespace const* const*>, std::__1::__wrap_iter<dd::Tablespace const* const*>, unsigned long>(std::__1::function<void (std::__1::__wrap_iter<dd::Tablespace const* const*> const&, std::__1::__wrap_iter<dd::Tablespace const* const*>6   mysqld                              0x000000010574e824 void* std::__1::__thread_proxy[abi:ue170006]<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct>>, Detached_thread, std::__1::function<void (std::__1::__wrap_iter<dd::Tablespace const* const*> const&, std::__1::__wrap_iter<dd::Tablespace const* const*> const&, unsigned long)>, std::__1::__wrap_iter<dd::Tablespace const* const*>, std::__1::__wrap_iter<dd::Tablespace const* const*>, unsi7   libsystem_pthread.dylib             0x000000019877ef94 _pthread_start + 136
8   libsystem_pthread.dylib             0x0000000198779d34 thread_start + 8
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:
* Install a fresh copy of MySQL Server
* Create and populate databases, for me, the problem starts between 30 and 40 databases for Drupal web sites
* Restart MySQL
[29 Jul 2024 16:58] Marc Reilly
You should use 8.4.2 that was released last week:

> InnoDB: In some cases, following the creation of a very large number of tables (8001 or more), the server could not be restarted successfully. (Bug #36808732)
References: This issue is a regression of: Bug #33398681.

https://dev.mysql.com/doc/relnotes/mysql/8.4/en/news-8-4-2.html

As per 8.4.1 release notes, that release is no longer available:
> This release is no longer available for download. It was removed due to a critical issue that could stop the server from restarting following the creation of a very large number of tables (8001, or more). Please upgrade to MySQL 8.4.2 instead.
https://dev.mysql.com/doc/relnotes/mysql/8.4/en/news-8-4-1.html
[29 Jul 2024 17:38] MySQL Verification Team
HI MR. Webster,

This bug is already fixed in the releases 8.0.39, 8.4.2 and 9.0.1.

Not a bug
[31 Jul 2024 10:29] MySQL Verification Team
Hi Mr. Webster,

You are truly welcome.