Thank you for this bug report. To properly diagnose the problem, we
need a short but complete example script to be able to reproduce
this bug ourselves. 

A proper reproducing script starts with <?php and ends with ?>,
is max. 10-20 lines long and does not require any external 
resources such as databases, etc. If the script requires a 
database to demonstrate the issue, please make sure it creates 
all necessary tables, stored procedures etc.

Please avoid embedding huge scripts into the report.

Hey,

there's no script execution necessary to cause the leak. It occurs even if I comment out "php_execute_script()" in my program.

But for completeness :-P:

<?php
print "Hello World";
?>

As the line numbers in the previous valgrind trace were incorrect due to changes I made to the PHP source to track the error and to see if the compiler globals destructor is actually called, here's another one with an unmodified library and no script execution (php_execute_script() commented out). Only initialization and deinitialization functions are called. This is the result after 10 request threads:

==1138== 
==1138== HEAP SUMMARY:
==1138==     in use at exit: 192,047 bytes in 2,902 blocks
==1138==   total heap usage: 1,145,600 allocs, 1,142,698 frees, 94,725,940 bytes allocated
==1138== 
==1138== 520 (216 direct, 304 indirect) bytes in 9 blocks are definitely lost in loss record 93 of 152
==1138==    at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==1138==    by 0x5B41B5: auto_global_copy_ctor (in /home/PREETZ/sathya/GitHub/Homegear/Homegear/homegear/src/homegear)
==1138==    by 0x5C85DB: zend_hash_copy (in /home/PREETZ/sathya/GitHub/Homegear/Homegear/homegear/src/homegear)
==1138==    by 0x5B3F6F: compiler_globals_ctor (in /home/PREETZ/sathya/GitHub/Homegear/Homegear/homegear/src/homegear)
==1138==    by 0x5B5324: zend_post_startup (in /home/PREETZ/sathya/GitHub/Homegear/Homegear/homegear/src/homegear)
==1138==    by 0x551E05: php_module_startup (in /home/PREETZ/sathya/GitHub/Homegear/Homegear/homegear/src/homegear)
.
.
.
==1138== 
==1138== 2,160 bytes in 90 blocks are definitely lost in loss record 135 of 152
==1138==    at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==1138==    by 0x5B41B5: auto_global_copy_ctor (in /home/PREETZ/sathya/GitHub/Homegear/Homegear/homegear/src/homegear)
==1138==    by 0x5C85DB: zend_hash_copy (in /home/PREETZ/sathya/GitHub/Homegear/Homegear/homegear/src/homegear)
==1138==    by 0x5B3F6F: compiler_globals_ctor (in /home/PREETZ/sathya/GitHub/Homegear/Homegear/homegear/src/homegear)
==1138==    by 0x54EF11: allocate_new_resource (in /home/PREETZ/sathya/GitHub/Homegear/Homegear/homegear/src/homegear)
==1138==    by 0x54F038: ts_resource_ex (in /home/PREETZ/sathya/GitHub/Homegear/Homegear/homegear/src/homegear)
.
.
.
==1138==    by 0x4E3F181: start_thread (pthread_create.c:312)
==1138== 
==1138== LEAK SUMMARY:
==1138==    definitely lost: 2,376 bytes in 99 blocks
==1138==    indirectly lost: 304 bytes in 9 blocks
==1138==      possibly lost: 0 bytes in 0 blocks
==1138==    still reachable: 189,367 bytes in 2,794 blocks
==1138==         suppressed: 0 bytes in 0 blocks
==1138== Reachable blocks (those to which a pointer was found) are not shown.
==1138== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==1138== 
==1138== For counts of detected and suppressed errors, rerun with: -v
==1138== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)

Cheers,

Sathya