Access violation when destroying H.264 Encoder

Access violation when destroying H.264 Encoder

In the IPP V6.0 sample for H.264 encoder, there seem to be a crash when using thedefault memory allocator. Calling the close method on the encoder will call BaseCodec:Close which will delete the memory allocator. The destructor of the H.264 encoder indirectly access the memory allocator through H264EncoderFrame_Destroy and H264EncoderFrame_deallocateParsedFrameData causing an access violation.

So if close is called before reaching the destructor of the encoder the codec will crash.


2 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.
Best Reply

Thanks for reporting onthe issue, I notified developers teamabout this.

Leave a Comment

Please sign in to add a comment. Not a member? Join today