php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #56137 [feature] consider of using HANDLE_BLOCK_INTERRUPTIONS?
Submitted: 2004-07-21 00:46 UTC Modified: 2014-02-28 12:31 UTC
Votes:1
Avg. Score:5.0 ± 0.0
Reproduced:0 of 1 (0.0%)
From: xuefer at 21cn dot com Assigned: rasmus (profile)
Status: Closed Package: APC (PECL)
PHP Version: Irrelevant OS: linux
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem:
29 - 24 = ?
Subscribe to this entry?

 
 [2004-07-21 00:46 UTC] xuefer at 21cn dot com 
Description:
------------
HANDLE_BLOCK_INTERRUPTIONS before LOCK
and HANDLE_UNBLOCK_INTERRUPTIONS after UNLOCK

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2004-09-07 00:28 UTC] rasmus@php.net 
Yeah, I actually have this in my own APC tree where I have turned the locking into a set of macros and redefined them to do things slightly differently.  I have yet to see a bug report that in any way suggests that this might be a problem though, but I agree that theoretically it could be.
 [2004-09-07 13:41 UTC] rasmus@php.net 
Committed to CVS
 [2004-11-08 10:57 UTC] xuefer at 21cn dot com 
this seems didn't solved conflict between zend_timeout and apc.

HANDLE_BLOCK_INTERRUPTIONS() only do with apache1.3
not against zend_timeout of ZendEngine
using HANDLE_BLOCK_INTERRUPTIONS still possible have possible timeout in the middle.
 [2004-11-08 11:43 UTC] xuefer at 21cn dot com 
maybe we can implement the BLOCKs ourself?
maybe we can use zend_try? zend_deactivate() did so,
but that's end of script exec. zend_try in the middle of script exec (e.g.: include()) may break zend_timeout(), unless we re-throw (zend_bailout again)

something i forgot to mention:
1. once a time, i got my script timedout on include() statement, i guess there's no place where php can spend such long time in "parsing"
this seems apc is waiting fot lock, i'm not sure, 
but the fact is "timeout still triggered"
well, this is just a "week"(can't make sure) instance.

2. recently, i get some "bad response" when a php file is updated, but re-request(auto done by browser) is ok, cached opcode is updated too(with new php run the page).
strange: no core dump.
by clearing the cache, everything is fine.
 [2014-02-28 12:31 UTC] krakjoe@php.net
-Status: Open +Status: Closed
 [2014-02-28 12:31 UTC] krakjoe@php.net 
Closing this, block interruptions are used, for 1.3, N/A for anything else.

The original request is therefore satisfied.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Fri Apr 26 08:01:30 2024 UTC