evas: fix memory leak with Efl.Canvas.Vg

Authored by cedric on Sep 26 2019, 10:19 PM.


evas: fix memory leak with Efl.Canvas.Vg

It is not correct to change the parent and hope that refcount will work
for you. The parent chain is a decision made by the user, not something
a widget can touch. Only ref count are to be used when given an outside
object. As things where not triggering destruction, there was also no
point where the image buffer would be getting to zero and be freed. This
commit also fix this.

Reviewers: Hermet, zmike

Reviewed By: Hermet

Subscribers: reviewers, committers

Tags: efl

Differential Revision: https://phab.enlightenment.org/D10169