Memory leak of NSAutoreleasePool due to mid-function return
In the function Control available in MobileVLCKit/ImportedSources/vlc/modules/video_output/ios2.m an object of class NSAutoreleasePool is created in the legacy alloc/init manner rather than by using the new @autoreleasepool block.
If a mid-function return happens such as might be the case for when cfg is NULL, the pool will most likely be leaked (some iOS versions may do better than others).
The legacy pattern for NSAutoreleasePool is used throughout the code base (both OS X and iOS) and should be replaced with the @autoreleasepool block which visually is better and handles throw/catch/return/break/goto issues. From a cursory inspection of the other uses of NSAutoreleasePool, they do not appear like they will leak in the same manner unless a throw happens.