Error in PHP GUI - 'Memory could not be read' problem when unloading php_mysqli.dll, SSL MySql problem

[Anton Hinxman]

See attached screen shot with SSL code and crash exit dialogue.

Remote MySQL SSL connection working but use of php_mysqli.dll crashes this product regardless of connection being OK.

XP SP3, 32 bit, IE8 update version 0

Would go for PHPExe but for problems like this.

PHP GUI also has fly over toolbar hint problems.

I guess that PHPExe will use the same methods so I hope that you get this sorted.

Regards,

Anton

[ZZEE Groups]

Hi Anton,

You can try another version of PHP here, PHP GUI uses a stock PHP got
from the official PHP site. You can download another PHP version and
try it.

PHPExe uses a modified PHP, and I am not sure if you get this kind of
error - you can try compiling a sample project and see if it works.

This error happens not because of MySQL connection but because of some
incorrect dll clean up code. For example, PHP v 5.2.5 works good
(php_mysql.dll is fine, except this php_mysqli.dll), but PHP 5.2.6 has
the same problem as you described with php_mysql.dll, so I think there
is a bug in PHP to MySQL code. Perhaps it is not noticeable with IIS
or Apache, because once they start they typically run forever, while
PHP GUI is being shutdown once the user exists their application.

--
Regards,
Paul.

Follow ZZEE on Facebook:
http://www.facebook.com/zzee.software

Feel free to become friends with Paul Slavic:
http://facebook.com/Paul.Slavic

[Anton Hinxman]

Thanks, you are correct and gave good indications to solve this problem.  Here is my fix:

Go to PHP download:  http://windows.php.net/download/ 
Pick to download the VC6 compiled Thread Safe windows binary: php-5.2.17-Win32-VC6-x86

  ... it is noted: VC6 x86 Thread Safe (2011-Mar-22 13:29:30)

Unzip ready to extract only the php_mysqli.dll

Rename the existing version of the file in the PHP GUI directory to, say,: php_mysqli.old.dll

Drop the new version into this same directory.

Test and verify that the problem has gone.

It appears that a jump from version 5.2.5.5 to 5.2.17.17 has fixed this problem.

I'll use the advanced version rather than the older one.

Kind regards,

Anton

[ZZEE Groups]

Anton,

Great, thank you. However I would recommend changing the whole of PHP,
not just one dll.

[Anton Hinxman]

Gave that a go but got back my delayed unloading GPF again.

It's kind of a regression testing problem.  If you change everything then you have to test everything and ones own project and resources do not have enough test script variations to do anything like that.  You swap all (upgrade) only to find a new problem further down the line in another new program yet to be written.  Swap out a limited single dll and you get unproven code conflicts only at that level but your program can cover unit testing on that scale.

What's the PHP API version policy concerning deprecated API changes between 5.2.n and any 5.2.n+ progressions?

Rgds,

Anton

[ZZEE Groups]

> Gave that a go but got back my delayed unloading GPF again.

For typical PHP installations this is not a problem, since it is being
turned off only when the computer is rebooted, or webserver needs
reloading. So perhaps they don't pay much attention to this.

> What's the PHP API version policy concerning deprecated API changes between
> 5.2.n and any 5.2.n+ progressions?

I am not sure, because I am not involved in PHP development. Hopefully
it is sane :)