Follow-up from "v4l2object: plug memory-leak"
The following discussion from !718 (merged) should be addressed:
-
@ndufresne started a discussion: Hmm, didn't remember about this function, this is a pretty horrible API imho. _open() should simply cleanup, or call that internally on failures. Do you think we can fix it while touching that ?