Edit report at https://bugs.php.net/bug.php?id=65562&edit=1
ID: 65562 Updated by: yohg...@php.net Reported by: rrh at newrelic dot com Summary: memory leak in zend_parse_arg Status: Feedback Type: Bug Package: Performance problem Operating System: all PHP Version: 5.5.3 Block user comment: N Private report: N New Comment: I suspect you have pointer issue. Valgrind does not handle ***(pointer to pointer to pointer) well. Check your hash handling code carefully, it may help. Previous Comments: ------------------------------------------------------------------------ [2013-08-26 23:02:10] johan...@php.net meant to write "your problem" :-) ------------------------------------------------------------------------ [2013-08-26 23:01:42] johan...@php.net https://github.com/johannes/php-src/commit/3bfe148c83d6c9b4134ac4fc5f6e0ae36f3f2c42 This might fix your issue. As you won't be telling whether this is our problem I can't properly test it. I'd welcome if you could test it and in future help providing patches. ------------------------------------------------------------------------ [2013-08-26 22:55:31] yohg...@php.net > It should be by using ext_skel shell script. It should be easy by using ext_skel shell script. ------------------------------------------------------------------------ [2013-08-26 22:54:27] yohg...@php.net If you are certain, please provide short and complete module code that leaks memory. (i.e. full module code that compiles as module) It should be by using ext_skel shell script. ------------------------------------------------------------------------ [2013-08-26 21:21:52] rrh at newrelic dot com I didn't provide code to show the issue because the issue is almost certainly independent of my module extension, and a quick inspection of the code looking at the control flow paths would show that efree isn't called on all paths leading to a return from the function. ------------------------------------------------------------------------ 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 https://bugs.php.net/bug.php?id=65562 -- Edit this bug report at https://bugs.php.net/bug.php?id=65562&edit=1
