I am observing that when encoding the longer 1080p sequences (Cactus, BasketballDrill, BQTerrace) on Windows, the encoder crashes at exactly the same frame number (=496), independent of QP value and sequence. This seems to coincide with the commit charge reaching about 2GB. Is this to be expected? (2GB sounds like a huge number given the frame size.) The issue is present in revision 17, but not in the initial stripped A124 software (revision 3 I believe).

The decoder seems to have similar problems, even for some class C sequences. The commit charge quickly increases to 2 GB after encoding a few frames.

Details:

• I am using the Beta script with unmodified configuration files and fast encoder settings (cft-fast).
• The problem is present on Windows XP/32-bit OS and on Windows 7/64 bit OS when compiling with “32-bit settings”.
• Compiling with “64 bit settings” and/or enabling large addresses when linking and running on 64-bit Windows OS seems to fix the problem for both the encoder and decoder (although the decoder slows down significantly when exceeding 4 GB working its way up to 18 GB commit charge  ).