Re: new/different problem in shutdown
| From: | Andi Gutmans | Date: | Fri, 06 Jul 2001 14:39:18 +0000 |
| Subject: | Re: new/different problem in shutdown | ||
| References: | 1 2 3 4 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-59094@lists.php.net to get a copy of this message | ||
At 04:31 PM 7/6/2001 +0200, Thies C. Arntzen wrote:
On Fri, Jul 06, 2001 at 05:12:07PM +0300, Andi Gutmans wrote: Thies, I have thought about your problem. Your patch fixed your test case but it won't fix all test cases. It is pretty much impossible to make sure on bailout (including exit() and errors) that all of the reference counts of the variables will go down to 0 even if we clean the call stack. This is due to necessary internal locking of variables in Zend.Because as I mentioned there might be locked variables which aren't in the call stack. This is what I could think of right now but there might be other problems too.i don't understand why we cant go thru the call-stack and del-ref all the arguments? we're shutting down anyhow - right?also i'm *not talking* about bail at all - bail dosn't work anyhow - and there's no good way to fix it IMHO. but what needs to work is calling exit() from a function if there are resources somewhere on the stack.
I think we need to think of a better way to handle resource shutdowns (maybe with priorities).Don't get me wrong. I really want to help you :) I just can't think of a great way right now. The only thing I could think of is making the resource shutdown smarter (will probably be quite a bit slower though). Andithis will be major headache, right?don't get me wrong, but i need this to get fixed elsewise using refcounts for dependicies is simply not working and i would have to think of something different - which would be a real shame.