Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Fix
-
10.2.6, 10.2(EOL), 10.3(EOL), 10.4(EOL)
-
None
-
win7 x64, 32GB ram, SSD
Description
If I set innodb-encryption-threads to any positive number, mariadb crashes a few minutes after the first innodb-background-scrub-data-check-interval occurs, with this in the log:
170601 8:26:17 [ERROR] mysqld got exception 0xc0000005 ;
|
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.6-MariaDB-log
|
key_buffer_size=134217728
|
read_buffer_size=131072
|
max_used_connections=0
|
max_threads=65537
|
thread_count=12
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 136026 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...
|
mysqld.exe!btr_scrub_free_page()[btr0scrub.cc:683]
|
mysqld.exe!btr_scrub_recheck_page()[btr0scrub.cc:720]
|
mysqld.exe!fil_crypt_rotate_page()[fil0crypt.cc:1827]
|
mysqld.exe!fil_crypt_rotate_pages()[fil0crypt.cc:1913]
|
mysqld.exe!fil_crypt_thread()[fil0crypt.cc:2160]
|
kernel32.dll!BaseThreadInitThunk()
|
ntdll.dll!RtlUserThreadStart()
|
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.
|
I have tried different values (0-8) for innodb-encryption-threads and all except 0 caused the crash approx 65 minutes after startup. When I set innodb-background-scrub-data-check-interval to 300, the crash occurs at 7-8 minute after startup, so something would appear to be triggered after, or as a result of, the check interval.
Unsetting (or explicitly setting to 0) innodb-encryption-threads (the only change in config) crash never occurs.
Attachments
Issue Links
- relates to
-
-
- Closed
-