MySQL Bugs: #45479: Performance Schema: error on shutdown

Bug #45479	Performance Schema: error on shutdown
Submitted:	13 Jun 2009 0:44	Modified:	10 Jul 2009 13:36
Reporter:	Peter Gulutzan	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: User-defined functions ( UDF )	Severity:	S3 (Non-critical)
Version:	6.0.12-alpha-perfschema	OS:	Linux (SUSE 10 / 64-bit)
Assigned to:		CPU Architecture:	Any

Description:
I'm using mysql-6.0-perfschema.

If I start the mysql-6.0-perfschema server
with default settings (that is, without
saying --performance_schema=1), then on
shutdown I see mysqld saying there's an error:
"Error in my_thread_global_end(): 2 threads didn't exit"

How to repeat:

Start the mysql-6.0-perfschema server with
libexec/mysqld --user=root
Then, on another connection, say
mysqladmin --user=root shutdown

With mysql-6.0-perfschema server I see:
"
090612 18:37:16 [Note] Event Scheduler: Purging the queue. 0 events
090612 18:37:16 [Note] libexec/mysqld: Shutdown complete

Error in my_thread_global_end(): 2 threads didn't exit
"

This does not happen if I use mysql-6.0.
With mysql-6.0 I see:
"
090612 18:33:26 [Note] libexec/mysqld: Normal shutdown

090612 18:33:26 [Note] Event Scheduler: Purging the queue. 0 events
090612 18:33:29  InnoDB: Starting shutdown...
090612 18:33:29  InnoDB: Shutdown completed; log sequence number 0 58669
090612 18:33:29 [Warning] Forcing shutdown of 2 plugins
090612 18:33:29 [Note] libexec/mysqld: Shutdown complete
"

This does not happen if I start with
mysqld --performance_schema=1.
With performance_schema=1 I see:
"
090612 18:35:30 [Note] libexec/mysqld: Normal shutdown

090612 18:35:30 [Note] Event Scheduler: Purging the queue. 0 events
090612 18:35:30 [Note] libexec/mysqld: Shutdown complete
"

Miguel Solorzano has shown that this doesn't occur on Windows.
I guess it's just a Linux-specific display that's equivalent
to the long-accepted messages about plugins.
Accordingly, I close my bug report as "Not a Bug".

whatever the reason, this is happening, and it a bug. either should be fixed or closed as a duplicate of another, plugin-specific, bug.

Thank you for the report.

I can not repeat described behavior with today sources on Linux. So i close the report as "Can't repeat". If you meet this again feel free to reopen the report.