PHP 5.2.1 Released

[jasonlitka]

An allowed memory size of 8MB for PHP 5.2.x is ridiculous. They raised the default to 16MB for a reason...

Improved memory manager and increased default memory limit (Dmitry)

The new memory manager allocates less memory and works faster than the previous incarnation. It allocates memory from the system in large blocks, and then manages the heap by itself. The memory_limit value in php.ini is checked, not for each emalloc() call (as before), but for actual blocks requested from the system. This means that memory_limit is far more accurate than it used to be, since the old memory manager didn't calculate all the memory overhead used by the malloc library.

Thanks to this new-found accuracy memory usage may appear to have increased, although actually it has not. To accommodate this apparent increase, the default memory_limit setting was also increased - from 8 to 16 megabytes.

EDIT: Also, you should try to take care of those "File does not exist" errors, they'll really slow you down.

[brvheart]

I dont know what is causing the file not found...

[brvheart]

An allowed memory size of 8MB for PHP 5.2.x is ridiculous. They raised the default to 16MB for a reason...



EDIT: Also, you should try to take care of those "File does not exist" errors, they'll really slow you down.

what setting do I need to up in the .ini?

[jasonlitka]

It was right in the text I posted.

...The memory_limit value in php.ini...

[brvheart]

I just wanted to be sure as my host asked me...thanks for the help

[WeArab.Net]

Help with PHP 5.2.1

Hello,

Here is the error I got when I upgrade to PHP 5.2.1 when I try to log to the admin Area.


Warning: preg_replace() [function.preg-replace]: Compilation failed: lookbehind assertion is not fixed length at offset 13 in /includes/functions_login.php on line 40

Here when I try to go to advanced reply.

Warning: preg_replace() [function.preg-replace]: Compilation failed: lookbehind assertion is not fixed length at offset 8 in /includes/functions_wysiwyg.php on line 149

Fatal error: Maximum execution time of 90 seconds exceeded in /usr/home/bbwww/www/includes/functions_wysiwyg.php on line 189

I'm using FreeBSD 6.2, Apache 2.3.4 and PHP 5.2.1

Thanks in advance for your kind help.

[Marco van Herwaarden]

I have never seen this error before, but doing a quick google on it, shows that more people have this problem with FreeBSD 6 & PHP 5.2.1. This might be a PHP bug.

[Scott MacVicar]

The PHP group says its not a bug in PHP is their report.

Are you using PHP from ports or compiled yourself?

[TommyBALL]

We upgraded yesterday as well on all apart from 1 of our servers since its having problems with open_basedir which we'll need to investigate.

Scott. Did you ever resolve this issue?

Regards
- Tommy

[Scott MacVicar]

It was to do with slashes at the end, or something similar.

/tmp/ didn't work but /tmp did, I'm not sure if that means it can access /tmpfoo or not.

I'll try and do it tonight when I deal with the APC updates.

[XtAzY]

I have never seen this error before, but doing a quick google on it, shows that more people have this problem with FreeBSD 6 & PHP 5.2.1. This might be a PHP bug.

i have freebsd 6.1 and php 5.2.1 running on my servers. No problems with it so far.

[WeArab.Net]

The PHP group says its not a bug in PHP is their report.

Are you using PHP from ports or compiled yourself?

Scott,

I built it from the ports.

[Scott MacVicar]

This is definately a FreeBSD bug as I've found a few on google all reporting this and they're running FreeBSD of some sort.

Can you downgrade to a previous version like 5.2.0 until its resolved?

I'll try installing FreeBSD 6.2 on a virtual machine and see what feedback I get.

[WeArab.Net]

Fix for FreeBSD VB and PHP 5.2.1

This is definately a FreeBSD bug as I've found a few on google all reporting this and they're running FreeBSD of some sort.

Can you downgrade to a previous version like 5.2.0 until its resolved?

I'll try installing FreeBSD 6.2 on a virtual machine and see what feedback I get.

Scott,

It turned out to not be a bug in FreeBSD nor vb, or PHP.

portupgrade -frR pcre-utf8-7.0

portupgrade -frR php5-pcre-5.2.1_3

apachectl restart

Later, my problems are blown away

[Scott MacVicar]

Looks like some packages weren't upgraded correctly when PHP was upgraded.

I did a fresh install of FreeBSD on a virtual machine and had zero issues after everything was installed, I can only assume it was the upgrade issue.