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

Filesort Aggregate Key Length Heap Overflow

    XMLWordPrintable

Details

    • Can result in hang or crash

    Description

      A query using ORDER BY on a large number of LONGBLOB columns can trigger a failure in the filesort implementation.

      heap overflow to libc Crash:

      Server version: 11.8.8-MariaDB-ubu2404 source revision: 46a8eb42a520193686d9a16d4cea4b3e002917e4

      The information page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/
      contains instructions to obtain a better version of the backtrace below.
      Following these instructions will help MariaDB developers provide a fix quicker.

      Attempting backtrace. Include this in the bug report.
      (note: Retrieving this information may fail)

      Thread pointer: 0x77d440000c68
      Fatal glibc error: malloc.c:2599 (sysmalloc): assertion failed: (old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)
      Fatal signal 6 while backtracing

      Reproduce:
      use reproduce.sql

      Attachments

        Activity

          People

            psergei Sergei Petrunia
            v3rdant Xingwang Xiang
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

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