Memory allocation error

[ueyome]

D:>avifenc 1.png 1.avif
Successfully loaded: 1.png
AVIF to be written: (Lossy)

• Resolution : 35920x11159
• Bit Depth : 8
• Format : YUV444
• Alpha : Not premultiplied
• Range : Full
• Color Primaries: 1
• Transfer Char. : 13
• Matrix Coeffs. : 6
• ICC Profile : Absent
• XMP Metadata : Absent
• Exif Metadata : Absent
• Transformations: None
• Progressive : Unavailable
• Gain map : Absent
  Encoding with initial settings: codec 'aom' speed [6], color quality [60 (Medium)], alpha quality [60 (Medium)], automatic tiling, 16 worker thread(s), please wait...
  ERROR: Failed to encode image: Encoding of color planes failed
  Diagnostics:
• aom_codec_encode() failed: Memory allocation error: Failed to allocate lag buffers

OS Win10
RAM 24G
Ver 1.3.0

[wantehchang]

@ueyome: Thank you for the bug report. Could you please attach the input image 1.png? Otherwise I can try to create a PNG file of the same size (35920x11159).

Could you past the output of avifenc --version? Thanks.

Very likey you ran into libaom's maximum allocation size, which is 8 GB by default. If you build libaom from source code, you can increase libaom's maximum allocation size by defining the macro AOM_MAX_ALLOCABLE_MEMORY to a larger value.

[vrabaud]

AVIF_DEFAULT_IMAGE_DIMENSION_LIMIT is used by avifenc right? 35920 is above that limit.

[ueyome]

C:\Users\Administrator>avifenc -V
Version: 1.3.0 (dav1d [dec]:1.5.1-0-g42b2b24, aom [enc]:3.12.1)
libyuv : available (1909)

[wantehchang]

Vincent: AVIF_DEFAULT_IMAGE_DIMENSION_LIMIT is only used by the decoder. It is not used by avifenc.

Also, the diagnostic message aom_codec_encode() failed: Memory allocation error: Failed to allocate lag buffers shows the libaom function aom_codec_encode() failed with the memory allocation error and the error message "Failed to allocate lag buffers".

[wantehchang]

@jzern

Following the instructions in a Stack Overflow page, I used the following ImageMagick command to generate a PNG file of size 35920x11159:

convert -size 35920x11159 xc:#990000 1.png

I found that this is caused by the following check in libaom's aom_scale/generic/yv12config.c:

static int realloc_frame_buffer_aligned(
    YV12_BUFFER_CONFIG *ybf, int width, int height, int ss_x, int ss_y,
    int use_highbitdepth, int border, int byte_alignment,
    aom_codec_frame_buffer_t *fb, aom_get_frame_buffer_cb_fn_t cb,
    void *cb_priv, const int y_stride, const uint64_t yplane_size,
    const uint64_t uvplane_size, const int aligned_width,
    const int aligned_height, const int uv_width, const int uv_height,
    const int uv_stride, const int uv_border_w, const int uv_border_h,
    bool alloc_pyramid, int alloc_y_plane_only) {
  ...

#if defined AOM_MAX_ALLOCABLE_MEMORY
    // The size of ybf->buffer_alloc.
    uint64_t alloc_size = frame_size;
#if CONFIG_AV1_ENCODER && !CONFIG_REALTIME_ONLY
    // The size of ybf->y_pyramid
    if (alloc_pyramid) {
      alloc_size += aom_get_pyramid_alloc_size(width, height, use_highbitdepth);
      alloc_size += av1_get_corner_list_size();
    }
#endif  // CONFIG_AV1_ENCODER && !CONFIG_REALTIME_ONLY
    // The decoder may allocate REF_FRAMES frame buffers in the frame buffer
    // pool. Bound the total amount of allocated memory as if these REF_FRAMES
    // frame buffers were allocated in a single allocation.
    if (alloc_size > AOM_MAX_ALLOCABLE_MEMORY / REF_FRAMES)
      return AOM_CODEC_MEM_ERROR;
#endif

I added that check https://aomedia-review.googlesource.com/c/aom/+/68961. This check is not intended to apply to the encoder. I also think I was misguided at that time; the decoder probably should defend against excessive memory consumption by relying on DECODE_WIDTH_LIMIT and DECODE_HEIGHT_LIMIT only.

[wantehchang]

@ueyome: You can work around this libaom issue by passing the -y 420 command-line option to avifenc. This will make avifenc use the YUV 4:2:0 format (instead of the default YUV 4:4:4 format) in the output AVIF. YUV 4:2:0 needs less memory than YUV 4:4:4 during encoding.

I will discuss with James Zern on how to fix the libaom issue. If you build avifenc from source code, you can delete the check I mentioned in #2842 (comment).

[ueyome]

If you build avifenc from source code, you can delete the check I mentioned in #2842 (comment).

I tried to delete it and build.

[tomek-szczesny]

I had the same issue with 16529x20874 jpg file, passing -y 420 indeed helps.

Successfully loaded: PLAN_von_DANZIG_1933_10K.jpg
AVIF to be written: (Lossy)
 * Resolution     : 16529x20874
 * Bit Depth      : 8
 * Format         : YUV444
 * Alpha          : Absent
 * Range          : Full
 * Color Primaries: 1
 * Transfer Char. : 13
 * Matrix Coeffs. : 6
 * ICC Profile    : Absent
 * XMP Metadata   : Present (5283 bytes)
 * Exif Metadata  : Present (7267 bytes)
 * Transformations: None
 * Progressive    : Unavailable
 * Gain map       : Absent
Encoding with initial settings: codec 'aom' speed [6], color quality [60 (Medium)], alpha quality [60 (Medium)], automatic tiling, 1 worker thread(s), please wait...
ERROR: Failed to encode image: Encoding of color planes failed
Diagnostics:
 * aom_codec_encode() failed: Memory allocation error: Failed to allocate lag buffers
avifenc failed, logged: PLAN_von_DANZIG_1933_10K.jpg