ID:               32475
 Updated by:       [EMAIL PROTECTED]
 Reported By:      lacey at lacey dot cc
-Status:           Open
+Status:           Feedback
 Bug Type:         IIS related
 Operating System: Windows XP
 PHP Version:      5CVS-2005-03-29
 New Comment:

Well, can you tell us too so we can fix it?



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

[2005-06-01 00:51:50] lacey at lacey dot cc

No.

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

[2005-05-27 09:04:00] [EMAIL PROTECTED]

Was it same place as said in bug #33118 ??


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

[2005-05-03 18:48:52] lacey at lacey dot cc

Found the Memory Leak.  Thanks for all the help.

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

[2005-04-05 02:27:41] lacey at lacey dot cc

Is there any feedback on this?  I've tried stepping into the code but
the debug files aren't jibing with the Source Code versions that I
have.

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

[2005-03-29 01:53:37] lacey at lacey dot cc

Yes.  Of course I will download those and do more testing.  I'll let
you know if I find out anything further.  But I've already given you
the exact subroutine.  It's the call to TSRMLS_FETCH() which calls
ts_resource_ex in trsm.c

ts_resouce_ex allocates the memory, and ts_free_thread somehow doesn't
free it all.  The memory keeps growing with the implementation of each
thread until the Server crashes.  I'd assume that's where you need to
look.  Or am I missing something here?

Jakub has explained the same scenario in this report as well.

http://bugs.php.net/bug.php?id=23331

Thanks.

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

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/32475

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

Reply via email to