push_nocopy object/string bug

[dmg0048]

If you push an object or string to another json object though any of the noncopy functions, when calling json_builder_free, this function tries to deallocate the .name and .ptr, which have not been allocated in this scenario.

I am posting this from my phone sorry for my brevity.

[LB--]

Hm, I suppose the API documentation is a bit lacking here, I think it is intended that these functions take ownership of the allocation from you, as that is how they are used internally in the implementation. Perhaps these functions should be renamed and maybe we can consider adding real nocopy that set a flag to indicate that they are not to be deallocated.