Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-18012

Supplied jemalloc results in immediate MariaDB Segfault on aarch64

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.0.37
    • 10.2.5
    • Compiling, Server
    • None
    • AWS aarch64, Amazon Linux AMI (EL7)

    Description

      mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
      [Note] /usr/sbin/mysqld (mysqld 10.0.37-MariaDB) starting as process 30510 ...
      <jemalloc>: Error in munmap(): Invalid argument
      [ERROR] mysqld got signal 11 ;
      

      This is likely to do with aarch64 on EL7 defaulting, against all sanity, to 64KB pages. Unfortunately, it is what it is.

      AFAICT, it is directly related to this bug:
      https://bugzilla.redhat.com/show_bug.cgi?id=1545539
      Unfortunately, that bug long postdates EL7, so a better, working jemalloc will likely need to be supplied.

      Also:
      MariaDB supplied jemalloc is the same as EL7 aarch64 EPEL jemalloc (same version, broken in the same way).

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              gbobic Gordan Bobic
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.