View Issue Details

IDProjectCategoryView StatusLast Update
0000150JVT JM H.264/AVC reference softwareencoderpublic2011-05-19 14:47
ReporterMatteo Naccari Assigned ToAlexis Michael Tourapis  
PrioritynormalSeveritycrashReproducibilityalways
Status resolvedResolutionfixed 
Product VersionJM 14.2 
Fixed in VersionJM 15.0 
Summary0000150: Further observations on the error #0000135
DescriptionDear H.264/AVC experts,

I want to add some comments on the ticket 0000135 (Encoder crashes in computeBiPredSAD2(), observed with IBBP coding). I have also experienced the same problem when encoding a 4CIF video sequence and using the EPZS ME algorithm. The encoder crashes after coding the 23rd frame of the City video sequence with a GOP type IBBP. I attach you the configuration file used whereby the encoder crash has been verified. I am using the software version JM14.2 and the MS Visual Studio .DOT NET 2003 with the Visual C++ version 7.0. By compiling the encoder in the debug modality I was able to find the code line that causes the encoder crash:

bi_diff = (*src_line++) - ((*ref1_line++ + *ref2_line++ + 1)>>1);

this line is inside the compute computeBiPredSAD1 function and the run-time execution stack is as follows:

computeBiPredSAD1
EPZSBiPredBlockMotionSearch
BiPredBlockMotionSearch
BlockMotionSearch
PartitionMotionSearch
encode_one_macroblock_high
encode_one_slice
code_a_plane
code_a_picture
frame_picture
encode_one_frame
encode_enhancement_layer
main

the ref2_line pointer it points to null (Bad Pointer).

I run the encoder with the following command line:

> lencod.exe -d encoder_main.cfg

Thank you again for the work you do in order to figure out the problem

With kind best regards

Matteo Naccari
TagsNo tags attached.

Relationships

child of 0000135 resolvedAlexis Michael Tourapis Encoder crashes in computeBiPredSAD2(), observed with IBBP coding 

Activities

2008-12-16 18:43

 

encoder_main.cfg (33,700 bytes)

Alexis Michael Tourapis

2008-12-16 19:54

developer   ~0000269

Please check the encoder again with version 15.0 after all appropriate parameters have been changed (FramesToBeEncoded, FrameSkip, IntraPeriod etc). We would recommend that you still keep BiPredSearch8x8 = 0 since that mode may still have issues even in this release.

Matteo Naccari

2008-12-16 21:58

reporter   ~0000270

Dear Alexis!

Actually if I had known that the version JM15.0 would have been released today I would not have disturbed you :). However, I will try your advices and I will let you know whether there are other problems.

All the best

Matteo

Karsten Suehring

2011-05-19 14:47

administrator   ~0000481

Seems this was fixed, but the bug not closed at the time.

Issue History

Date Modified Username Field Change
2008-12-16 18:43 Matteo Naccari New Issue
2008-12-16 18:43 Matteo Naccari File Added: encoder_main.cfg
2008-12-16 19:54 Alexis Michael Tourapis Note Added: 0000269
2008-12-16 21:58 Matteo Naccari Note Added: 0000270
2008-12-16 22:36 Karsten Suehring Relationship added child of 0000135
2008-12-16 22:37 Karsten Suehring Status new => assigned
2008-12-16 22:37 Karsten Suehring Assigned To => Alexis Michael Tourapis
2011-05-19 14:47 Karsten Suehring Note Added: 0000481
2011-05-19 14:47 Karsten Suehring Status assigned => resolved
2011-05-19 14:47 Karsten Suehring Fixed in Version => JM 15.0
2011-05-19 14:47 Karsten Suehring Resolution open => fixed