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

SIGSEGV in Item_field::fix_fields when using LEAD...OVER

Details

    Description

      On second select, server crashes.

      Attachments

        Issue Links

          is caused by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-25631 Crash executing query with VIEW, aggregate and subquery

          • Major - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-31296 Crash in Item_func::fix_fields when prepared statement with subqueries and window function is executed with sql_mode = ONLY_FULL_GROUP_BY

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            Transition Time In Source Status Execution Times
            Roel Van de Paar made transition -
            Open Needs Feedback
            		86d 22h 26m 1
            Daniel Black made transition -
            Needs Feedback Open
            		4d 3h 39m 1
            Alice Sherepa made transition -
            Open Confirmed
            		13h 26m 1
            Daniel Black made transition -
            Confirmed In Progress
            		150d 12h 55m 1
            Daniel Black made transition -
            In Progress In Review
            		2m 31s 1
            Dmitry Shulga made transition -
            In Review Stalled
            		3d 56m 1
            Daniel Black made transition -
            Stalled Closed
            		54m 28s 1

            People

              danblack Daniel Black
              vk4ypb Peter Bennett
              Votes:
              1 Vote for this issue
              Watchers:
              8 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.