bRet = tex~~>initWithStringif this fails, tex~~>release() is never called and tex gets leaked. I’m seeing this in Instruments but I haven’t constructed a specific example to test it. Hopefully this gets the devs attention.

Note: using new() instead of create(). This means no reference counter logic is called. tex is also implicitly “retained” because of this.

tex~~>release;Actually tries to deref something that we use the reference counter create function on. But even if we do technically have a retained tex, we never actually call the reference counter, and the reference counter is never updated.Not to mention the profiler sees no sign of a delete because we’re using release instead.And so we get a leak message.Can someone confirm if the object is actually removed and we can safely ignore this? If not, I’ll see what happens if I just throw a ::create inside CCTexture2D.Edit: nope, cloning a CCobject::create inside CCTexture2D doesn’t work~~ all I get is a “not implement” message when it tries to call m_pobTexture->getContentSize().