MySQL Bugs: #7403: error "Forcing close of thread 1 user: 'xxx'"

Bug #7403	error "Forcing close of thread 1 user: 'xxx'"
Submitted:	18 Dec 2004 13:24	Modified:	10 Jan 2013 10:59
Reporter:	Victoria Reznichenko	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Server: Windows	Severity:	S3 (Non-critical)
Version:	4.0, 5.0.40, 5.1.42-bzr	OS:	Windows (Windows)
Assigned to:		CPU Architecture:	Any

Description:
On Windows if you have opened connections, you get the following errors during shutdown:

"Forcing close of thread 1  user: 'xxx'"

These errors are written to the error log only on Windows.

How to repeat:
1. connect to the MySQL server
2. shutdown it

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/27091

Fixed in 4.1.14 and 5.0.10

The fix for the bug forces safe_mutex assertion failure in 5.0.
The bug needs a better fix, at least in 5.0.

Marked back as documenting.  Guilhem created a new bug report for the fix and will be pushing a fix for it.

Noted in 4.1.14, 5.0.10 changelogs.

Bug #48879 is marked as a duplicate of this one.

4.1/5.0 changelog entries removed at request of Support, since there is no evidence that this bug was ever actually fixed:

http://lists.mysql.com/commits/95035

Left bug status unchanged.

The bug has not yet been fixed. I disabled the changelog entry until such time as it is.

Oops, Jon beat me to it.

workaround, set in my.ini: log_warnings=0

We wont't fix this because:

a)This is an old bug, no blocked customer.

b)Removing the warning is simple, removing the reason why warning is occurring is hard.