Bug 252636 - databases/mysql57-server using libtcmalloc fails when upgrading to google-perftools-2.8.1
Summary: databases/mysql57-server using libtcmalloc fails when upgrading to google-per...
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: Jochen Neumeister
Depends on:
Reported: 2021-01-13 10:13 UTC by Jorrit
Modified: 2021-04-11 16:36 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (joneum)


Note You need to log in before you can comment on or make changes to this bug.
Description Jorrit 2021-01-13 10:13:23 UTC
I don't know if this problem is with mysql57-server OR with google-perftools. Because of swap-problems I'm using libtcmalloc (as described in https://forums.freebsd.org/threads/freebsd-12-x-and-mysql-5-7-and-importing-file-with-lots-of-small-lines-exhaust-ram-and-swap.72733/) with mysql57-server-5.7.32 on 12.2-RELEASE-p2. However, since upgrading to google-perftools-2.8.1 mysql-server refuses to start.

Happened on production server. Could repeat it on development server after upgrading to same versions mysql-server/google-perftools.

MySQL error log:

2021-01-13T09:55:39.254557Z 0 [Note] InnoDB: Last MySQL binlog file position 0 432222, file name mysql-bin.000510
09:55:39 UTC - mysqld got signal 10 ;
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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 125490 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 = 0 thread_stack 0x40000
0x1452188 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0x13ad15e <handle_fatal_signal+0x2be> at /usr/local/libexec/mysqld
0x801f28b70 <_pthread_sigmask+0x530> at /lib/libthr.so.3
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.
2021-01-13T09:55:39.6NZ mysqld_safe mysqld from pid file /var/db/mysql/bsdvm03.pid ended