We have moved our forum to GitHub Discussions. For questions about Phalcon v3/v4/v5 you can visit here and for Phalcon v6 here.
  1. Home
  2. Show to Community

php5.6.26-phalcon3 :[debian 8.5]: memory leaks detected


// "[Sat Sep 24 06:32:35 2016]  Script:  '-'"
[24-Sep-2016 06:32:35] WARNING: [pool www] child 7 said into stderr: "/tmp/cphalcon/build/php5/64bits/phalcon.zep.c(23687) :  Freeing 0x7F32E7660FF8 (32 bytes), script=-"
[24-Sep-2016 06:32:35] WARNING: [pool www] child 7 said into stderr: "Last leak repeated 1 time"
[24-Sep-2016 06:32:35] WARNING: [pool www] child 7 said into stderr: "[Sat Sep 24 06:32:35 2016]  Script:  '-'"
[24-Sep-2016 06:32:35] WARNING: [pool www] child 7 said into stderr: "/tmp/cphalcon/build/php5/64bits/phalcon.zep.c(86417) :  Freeing 0x7F32E7698EF8 (32 bytes), script=-"
[24-Sep-2016 06:32:35] WARNING: [pool www] child 7 said into stderr: "[Sat Sep 24 06:32:35 2016]  Script:  '-'"
[24-Sep-2016 06:32:35] WARNING: [pool www] child 7 said into stderr: "/tmp/cphalcon/build/php5/64bits/phalcon.zep.c(17786) :  Freeing 0x7F32E769F640 (32 bytes), script=-"
[24-Sep-2016 06:32:35] WARNING: [pool www] child 7 said into stderr: "[Sat Sep 24 06:32:35 2016]  Script:  '-'"
[24-Sep-2016 06:32:35] WARNING: [pool www] child 7 said into stderr: "/tmp/cphalcon/build/php5/64bits/phalcon.zep.c(21762) :  Freeing 0x7F32E76C5868 (32 bytes), script=-"
[24-Sep-2016 06:32:35] WARNING: [pool www] child 7 said into stderr: "[Sat Sep 24 06:32:35 2016]  Script:  '-'"
[24-Sep-2016 06:32:35] WARNING: [pool www] child 7 said into stderr: "/tmp/cphalcon/build/php5/64bits/phalcon.zep.c(69571) :  Freeing 0x7F32E76C6CF0 (32 bytes), script=-"
[24-Sep-2016 06:32:35] WARNING: [pool www] child 7 said into stderr: "=== Total 6 memory leaks detected ==="

help me please


145.0k
edited Sep '16

32 bytes

I wouldn't care about it. If you have php compiled as debug with memory leak detection this can be a reason why you have memory leaks, at leasy from my experience.

also this is not telling much. Better provide log from valgrind.



79.0k

It shouldn't leak.

Perhaps it could be your use case / how you init your application etc.