Re: [E-devel] valgrind still reachable memory somewhere between Ecore and Eo

2013-10-02 Thread Yakov Goldberg
Got it. It's not ecore_idle_enterer class, it's me sending only this output. If run elementary_test with valgrind, it will happen for each elm class. Yakov. On 10/02/2013 12:52 PM, Tom Hacohen wrote: > On 02/10/13 09:15, Yakov Goldberg wrote: >> I was trying to play with very simple ELM applica

Re: [E-devel] valgrind still reachable memory somewhere between Ecore and Eo

2013-10-02 Thread Tom Hacohen
On 02/10/13 09:15, Yakov Goldberg wrote: > I was trying to play with very simple ELM application, like this :) > > === > #include > > int > main(int argc, char **argv) > { > elm_init(argc, argv); > elm_shutdown(); > return 0; > } > === > > and noti

[E-devel] valgrind still reachable memory somewhere between Ecore and Eo

2013-10-02 Thread Yakov Goldberg
I was trying to play with very simple ELM application, like this :) === #include int main(int argc, char **argv) { elm_init(argc, argv); elm_shutdown(); return 0; } === and noticed lot of "still reachable" memory: ==11408== 256 bytes in 1 blocks a