https://community.intel.com/t5/Intel-Integrated-Performance/Access-violation-when-destroying-H-264-Encoder/m-p/894668#M11924 <DIV style="margin:0px;">Thanks for reporting onthe issue, I notified developers teamabout this.</DIV> <DIV style="margin:0px;">Regards,<BR /> Vladimir</DIV> <DIV style="margin:0px;"></DIV> <P></P> Tue, 02 Dec 2008 13:07:11 GMT Vladimir_Dudnik 2008-12-02T13:07:11Z https://community.intel.com/t5/Intel-Integrated-Performance/Access-violation-when-destroying-H-264-Encoder/m-p/894667#M11923 <P>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.</P> <P>So if close is called before reaching the destructor of the encoder the codec will crash.</P> <P>Emmanuel</P> Wed, 26 Nov 2008 15:01:12 GMT https://community.intel.com/t5/Intel-Integrated-Performance/Access-violation-when-destroying-H-264-Encoder/m-p/894667#M11923 Emmanuel_W_ 2008-11-26T15:01:12Z https://community.intel.com/t5/Intel-Integrated-Performance/Access-violation-when-destroying-H-264-Encoder/m-p/894668#M11924 <DIV style="margin:0px;">Thanks for reporting onthe issue, I notified developers teamabout this.</DIV> <DIV style="margin:0px;">Regards,<BR /> Vladimir</DIV> <DIV style="margin:0px;"></DIV> <P></P> Tue, 02 Dec 2008 13:07:11 GMT https://community.intel.com/t5/Intel-Integrated-Performance/Access-violation-when-destroying-H-264-Encoder/m-p/894668#M11924 Vladimir_Dudnik 2008-12-02T13:07:11Z