Ticket #54 (reopened defect)

Opened 2 years ago

Last modified 2 years ago

eAccelerator 0.9.5b2/dev and PHP5.1.2 non-functional

Reported by: Jonathan Stanley Assigned to: bart
Priority: blocker Milestone: 0.9.6
Component: eAccelerator Version: 0.9.5
Keywords: Cc:

Description (Last modified by bart)

Had been running eAccelerator 0.9.5b1 without (much) issue on my Debian 3.1 box with Apache/1.3.33 Ben-SSL/1.55 with PHP5.1.2.

Decided to try the latest SVN code (as of 13th April, 22:30 GMT) yet when Apache is restarted, all PHP pages return a blank page with a very odd memory exhaustion error, such as this one relating to WordPress?: 

[Thu Apr 13 22:19:17 2006] [error] PHP Fatal error:  Allowed memory size of 67108864 bytes exhausted (tried to allocate -1073799975 bytes) in ./wp-settings.php on line 103
[Thu Apr 13 22:19:19 2006] [error] PHP Fatal error:  Allowed memory size of 67108864 bytes exhausted (tried to allocate -1073799975 bytes) in ./wp-settings.php on line 103
[Thu Apr 13 22:20:07 2006] [error] PHP Fatal error:  Allowed memory size of 67108864 bytes exhausted (tried to allocate -1073799975 bytes) in ./wp-settings.php on line 103
[Thu Apr 13 22:20:21 2006] [error] PHP Fatal error:  Allowed memory size of 67108864 bytes exhausted (tried to allocate -1073799975 bytes) in ./wp-settings.php on line 103
[Thu Apr 13 22:20:39 2006] [error] PHP Fatal error:  Allowed memory size of 67108864 bytes exhausted (tried to allocate -1073799975 bytes) in ./wp-settings.php on line 103

Compiling and installing eAccelerator 0.9.5b2 causes the same issue too.

Change History

04/14/06 02:18:47 changed by Jonathan Stanley

  • version set to 0.9.5.
  • milestone deleted.

04/14/06 06:47:08 changed by anonymous

same here with PHP 5.1.3rc2, apache 2.2.0, gcc 4.1.0, glibc 3.4

04/14/06 11:46:16 changed by bart

  • description changed.

04/14/06 11:47:40 changed by bart

  • owner changed from somebody to bart.
  • status changed from new to assigned.
  • milestone set to 0.9.5.

Can you tell me the wordpress version you are using? Do you still have this problem with the optimizer disabled? It sounds like wordpress gets into an infinite loop because of an optimization that goes wrong. Does it happen on the first run before the script is cached?

04/15/06 03:09:52 changed by Jonathan Stanley

The WordPress? version I'm running is mostly 1.5.x branch ( http://svn.automattic.com/wordpress/branches/1.5/ ). As I recall, it happens on all pages on first load. Disabling the optimiser temporarily "fixed" it as I downgraded to a "known good" version. :)

05/08/06 13:06:47 changed by bart

  • status changed from assigned to closed.
  • resolution set to worksforme.

I havn't got any problems with wp 1.5 nor with wp from trunk. Because you don't want to try disabling the optimizer with the code that didn't function for you and I can't reproduce this, I'm closing this bug.

05/24/06 00:18:14 changed by anonymous

  • component changed from eAccelerator to Encoder.

09/19/06 15:52:18 changed by VinVent

  • status changed from closed to reopened.
  • resolution deleted.
  • component changed from Encoder to eAccelerator.

I have the same error : "Fatal error: Allowed memory size of 524288000 bytes exhausted (tried to allocate -2131466260 bytes) in /www/haricow/core/Module.class.php on line 118".

This occurs on 'require_once', especially : 

$view = isset($view) ? file_get_contents($parentView) : HRC_VIEW;
$path = HRC_VIEW_DIRECTORY.'/'.$view.'/module/'.$element.'/'.$fileName.'.class.php';

if(is_file($path)) {
	require_once $path; // Line
	break;
}

I got the same error here too : 

$classLoad = 'Db'.ucfirst($type);
require_once 'module/Db/Db'.ucfirst($type).'.class.php';

09/19/06 16:07:21 changed by VinVent

I made more tests and it appears that this error does not occur when SHM only is enabled.

10/16/06 17:56:47 changed by franck

ignore this message : test to see lag in trac ticket manager

11/04/06 14:21:07 changed by bart

  • milestone changed from 0.9.5 to 0.9.6.