Hello internals,
i just stumbled over a strange issue while testing. Some of my tests
have exit(0) at the end for easier test verification. Now i found a new
one that has a few memleaks but only reports them if i drop that exit(0)
line. Is this something we need to fix (e.g. exit() omits leakage info)?
--
Best regards,
Marcus mailto:mail@marcus-boerger.de
Marcus Boerger wrote:
i just stumbled over a strange issue while testing. Some of my tests
have exit(0) at the end for easier test verification. Now i found a new
one that has a few memleaks but only reports them if i drop that exit(0)
line. Is this something we need to fix (e.g. exit() omits leakage info)?
Sorry, but I cannot speak for exit(), but I usually replace all occurrences of
#if PHP_WIN32
OutputDebugString(...);
#else
fprintf(stderr, ...);
#endif
with just fprintf(stderr, ...) to see any mem-leaks on Win32-CLI.
JFYI.
Regards,
Mike
That should probably just be:
#if PHP_WIN32
OutputDebugString(...);
#endif
fprintf(stderr, ...);
Sorry, but I cannot speak for exit(), but I usually replace all occurrences of
#if PHP_WIN32
OutputDebugString(...);
#else
fprintf(stderr, ...);
#endifwith just fprintf(stderr, ...) to see any mem-leaks on Win32-CLI.
Hello Wez,
i used linux so there seems to be a problem with either flushing or the
fprintf not being called at all.
regards
marcus
Monday, June 20, 2005, 10:55:43 PM, you wrote:
That should probably just be:
#if PHP_WIN32
OutputDebugString(...);
#endif
fprintf(stderr, ...);
Sorry, but I cannot speak for exit(), but I usually replace all occurrences of
#if PHP_WIN32
OutputDebugString(...);
#else
fprintf(stderr, ...);
#endifwith just fprintf(stderr, ...) to see any mem-leaks on Win32-CLI.
--
--
Best regards,
Marcus mailto:mail@marcus-boerger.de
When exit() is called, like any other case in which zend_bailout() is used,
there can be memory blocks which will not be 'properly' freed, and we have
to rely on the memory manager to free it. So the fact leaks are not shown
in case of exit() is intentional.
Zeev
At 05:19 20/06/2005, Marcus Boerger wrote:
Hello internals,
i just stumbled over a strange issue while testing. Some of my tests
have exit(0) at the end for easier test verification. Now i found a new
one that has a few memleaks but only reports them if i drop that exit(0)
line. Is this something we need to fix (e.g. exit() omits leakage info)?--
Best regards,
Marcus mailto:mail@marcus-boerger.de
Hello Zeev,
thanks for clarifying. Any chance we could change that for
"normal/unproblemeatic" exit()s in the future with run-tests
in mind?
marcus
Wednesday, June 22, 2005, 4:03:35 PM, you wrote:
When exit() is called, like any other case in which zend_bailout() is used,
there can be memory blocks which will not be 'properly' freed, and we have
to rely on the memory manager to free it. So the fact leaks are not shown
in case of exit() is intentional.
Zeev
At 05:19 20/06/2005, Marcus Boerger wrote:
Hello internals,
i just stumbled over a strange issue while testing. Some of my tests
have exit(0) at the end for easier test verification. Now i found a new
one that has a few memleaks but only reports them if i drop that exit(0)
line. Is this something we need to fix (e.g. exit() omits leakage info)?