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

thd_destructor_proxy() hangs on shutdown after aborted startup

    XMLWordPrintable

Details

    Description

      When MariaDB Server is started with an invalid option that causes InnoDB startup to be aborted, the thd_destructor_proxy() thread (which was introduced in MDEV-5800) gets stuck, causing an error message and assertion failure:

      Error in my_thread_global_end(): 1 threads didn't exit
      		 
       
      		 
      mysqld: /home/marko/mariadb/server/sql/mysqld.cc:2154: void mysqld_exit(int): Assertion `global_status_var.global_memory_used == 0' failed.

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. MDEV-11689 Server shuts down in unclean fashion after failing to start with a wrong value of innodb_undo_tablespaces

          • Major - Major loss of function.
          • Closed
          is caused by

          Task - A task that needs to be done. MDEV-5800 indexes on virtual (not materialized) columns

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Activity

            People

              serg Sergei Golubchik
              marko Marko Mäkelä
              Votes:
              0 Vote for this issue
              Watchers:
              1 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.