Using [abusing] static Value gives memory leak


#1

** PLEASE NOTE **  I've worked around the issue by doing away with the static Value. 

The post below was pieced together while I experimented with reproducing and fixing the issue.   I'm still curious as to why didn't work so here it is...

 

 

 

I have a really simple dialog class with a static Value member (x) and in the custom constructor code I refer a TextEditor to it:   

textX->getTextValue().referTo( x );

but it's leaking memory.  It looks like a String object because the TextEditor contents were "1234567890" but it's hard to track via the allocation number alone.


Detected memory leaks!
Dumping objects ->
{42276} normal block at 0x02450650, 23 bytes long.
 Data: <        12345678> 00 00 00 00 0C 00 00 00 31 32 33 34 35 36 37 38 

 

I'm launching the window asynchronously so a new instance is created each time.