ID: 41301
User updated by: glen at aquarius dot com dot au
Reported By: glen at aquarius dot com dot au
Status: Bogus
Bug Type: *Database Functions
Operating System: win200 server
PHP Version: 5.2.2
New Comment:
The following comments have been made in the MySQL Bug reports for this
bug:
[14 May 3:34] Siew Pui Tong
I have upgraded to PHP 5.2.2.
I cfm that using libmysql.dll from 5.2.1, instead of 5.2.2 solved the
pbm.
------------------------------------------------------------------
[13 May 23:20] Nathan (York Networks)
I started seeing this bug after upgrading from PHP 5.1.x to 5.2.2.
Interestingly, copying the libmysql.dll from the 5.1.x version in to
the 5.2.2 release appears to have resolved the issue at list until the
underlying problem is addressed.
---------------------------------------------------------------------
I have also changed the file and both phpBB3 and WordPress are now
seemingly working fine.
Previous Comments:
------------------------------------------------------------------------
[2007-05-09 16:32:52] [EMAIL PROTECTED]
We don't call my_thread_init, or anything starting with my_thread:
[EMAIL PROTECTED]:~/dev/php/php-5.2dev$ grep -r my_thread *
[EMAIL PROTECTED]:~/dev/php/php-5.2dev$
------------------------------------------------------------------------
[2007-05-09 15:55:45] glen at aquarius dot com dot au
This is becoming a big issue over at MySQL Headquarters :-) Quite a
number of programs utilising PHP and NOT commenting out the MySQL
library are falling over. NOTE: You don't actually have to use MySQL -
just having it enabled in PHP causes the problem as well.
The latest:
[9 May 17:43] Sergei Golubchik
Strictly speaking, this is not MySQL bug. This is a client bug - a
client application (PHP, probably) linked with libmysqlclient calls
my_thread_init() but does not call my_thread_end() as appropriate
(doesn't call at all or calls too late). MySQL client library detects
this and issues a warning.
On the other hand, we can just remove the check and let buggy
applications to fail some other way. Not calling my_thread_end() is a
guaranteed memory leak. Calling it too late could easily crash the
application.
------------------------------------------------------------------------
[2007-05-06 22:54:31] glen at aquarius dot com dot au
The problem is caused by MySQL and has been confirmed (Bug# 25621). It
will apparently be fixed in the next release.
In the meantime, if you are using PHP and do not use MySQL then you can
disable MySQL by commenting out the reference at the end of php.ini eg:
[PHP_MYSQL]
;extension=php_mysql.dll
------------------------------------------------------------------------
[2007-05-06 12:44:47] glen at aquarius dot com dot au
Thanks for that - much appreciated.
------------------------------------------------------------------------
[2007-05-06 10:34:15] [EMAIL PROTECTED]
>Error in my_thread_global_end(): 5 threads didn't exit
There is no such function nor error message in PHP.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/41301
--
Edit this bug report at http://bugs.php.net/?id=41301&edit=1
