#20282 [Fbk->NoF]: COM memory leak

ID: 20282 Updated by: sniper@php.net Reported By: sven.packmor@tz-mikroelektronik.de -Status: Feedback +Status: No Feedback Bug Type: COM related Operating System: Win2000/XP PHP Version: 4.2.3 New Comment: No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you. Previous Comments: ------------------------------------------------------------------------ [2003-01-29 19:56:08] phanto@php.net Please try using this CVS snapshot: http://snaps.php.net/php4-STABLE-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-STABLE-latest.zip try a stable release snapshot ------------------------------------------------------------------------ [2003-01-18 16:11:35] phanto@php.net suspended php4 development to look forward to a more stable php5 ------------------------------------------------------------------------ [2002-12-20 11:12:49] sven.packmor@tz-mikroelektronik.de Hi there, it's possible that we will hire a developer to fix this bug. If somebody is in the mood to do bugfixing, please contact me under sven.packmor@tz-mikroelektronik.de. Sven ------------------------------------------------------------------------ [2002-12-09 15:31:19] phanto@php.net as soon as anybody is in the mood to fix it ... erm, and 'Hi, how about bugfixing ?' or 'Is it possible to get a solution soon?' for sure doesn't bring anyone into that mood. but you have full access to the sources and can always send in a patch. harald ------------------------------------------------------------------------ [2002-12-09 03:21:45] sven.packmor@tz-mikroelektronik.de Hi Derick, if we don't hire an PHP developer, when do you think the bug will be fixed? Is there a roadmap for this bug? Sven ------------------------------------------------------------------------ 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/20282 -- Edit this bug report at http://bugs.php.net/?id=20282&edit=1