ID:               42220
 User updated by:  mv at binarysec dot com
 Reported By:      mv at binarysec dot com
-Status:           Feedback
+Status:           Open
 Bug Type:         Scripting Engine problem
 Operating System: linux
 PHP Version:      5CVS-2007-08-06 (CVS)
 New Comment:

There is no php.ini defined, i used Apache 2.2.3 -worker- + PHP_5_2 as
a module (cvs).
In fact i have saw the problem 2 times on a core 2 duo and many times
on  my quad core which i used to develope.

I use nikto & curl to load the server.

Have fun ;)


Previous Comments:
------------------------------------------------------------------------

[2007-08-12 14:13:42] [EMAIL PROTECTED]

And you didn't mention anything about how you've configured PHP and
under what webserver you're using it..

------------------------------------------------------------------------

[2007-08-12 14:13:05] [EMAIL PROTECTED]

The question is: Do you get it at all when APC is NOT loaded?

------------------------------------------------------------------------

[2007-08-06 12:06:56] mv at binarysec dot com

Description:
------------
Hi,

I have a thread safe problem with the true global list_destructors,
sometimes i got some messages like :
<b>Warning</b>:  Unknown list entry type in request shutdown
(1882088036) in <b>Unknown</b> on line <b>0</b><br />

It happens very randomly i don't really know how to reproduce the code,
but APC looks to help to get the error.

I had a look at list_entry_destructor() zend_list.c +374 why does this
function generate this error and it looks that list_destructors isn't
thread safe.

I **need** to fix that because sometimes you could get a blank page
with APC.


Reproduce code:
---------------
none

Expected result:
----------------
none

Actual result:
--------------
<b>Warning</b>:  Unknown list entry type in request shutdown
(1882088036) in <b>Unknown</b> on line <b>0</b><br />


------------------------------------------------------------------------


-- 
Edit this bug report at http://bugs.php.net/?id=42220&edit=1

Reply via email to