Skip to content

This test is silly. All it does is fill up the VRAM until it's completely full, and then fails. #802

Description

@Ichimikichiki

Screenshot_2024-06-07_01-51-41

What a stupid test. Just fills up the VRAM until there's none left. What is the point of this?

[AVHWDeviceContext @ 0x25bfe376ac0] cu->cuMemAlloc(&data, size) failed -> CUDA_ERROR_OUT_OF_MEMORY: out of memorypeed=21.6x    
[AVHWDeviceContext @ 0x25bfe376ac0] cu->cuMemAlloc(&data, size) failed -> CUDA_ERROR_OUT_OF_MEMORY: out of memory
[hwupload @ 0x25bfecb1540] Failed to allocate frame to upload to.
[vf#0:0 @ 0x25bfe31acc0] Error while filtering: Cannot allocate memory
Failed to inject frame into filter network: Cannot allocate memory
Error while filtering: Cannot allocate memory
[out#0/null @ 0x25bfe35a340] video:707kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
[out#1/null @ 0x25bfec77d00] video:30123kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
[out#2/null @ 0x25bfec94d80] video:30123kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
[out#3/null @ 0x25bfecb1f00] video:30124kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
[out#4/null @ 0x25bfeccf0c0] video:30124kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
[out#5/null @ 0x25bfecec2c0] video:30124kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
[out#6/null @ 0x25bfed09580] video:30124kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
[out#7/null @ 0x25bfed266c0] video:30132kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
[out#8/null @ 0x25bfed43800] video:30133kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
frame= 1250 fps= 13 q=8.0 Lq=9.0 q=9.0 q=9.0 q=9.0 q=9.0 q=9.0 q=9.0 q=9.0 size=N/A time=00:35:05.72 bitrate=N/A speed=21.6x    
Conversion failed!

Activity

  1. temp-byte commented on Jun 7, 2024

    @temp-byte

    You might want to try different version and/or provider of ffmpeg.
    I ran into the same kind of issue where my RAM would just fill up to a certain point and the test failed.
    This did not occur when I used the ffmpeg from directory of Shotcut, OBS Studio or ffmpeg from gyan.dev

  2. ABelliqueux commented on Jun 11, 2024

    @ABelliqueux

    Same here on Manjaro Linux:

    $ uname -a 
    Linux foo 6.6.30-2-MANJARO #1 SMP PREEMPT_DYNAMIC Wed May  8 17:46:43 UTC 2024 x86_64 GNU/Linux
    $ ffmpeg -version
    ffmpeg version n6.1.1 Copyright (c) 2000-2023 the FFmpeg developers
    built with gcc 13.2.1 (GCC) 20230801
    [...]
    $ nvidia-smi
    Tue Jun 11 18:17:18 2024       
    +-----------------------------------------------------------------------------------------+
    | NVIDIA-SMI 550.78                 Driver Version: 550.78         CUDA Version: 12.4     |
    [...]
    |   0  NVIDIA GeForce GTX 1050        Off |   00000000:01:00.0 Off |                  N/A |
    
  3. moogoos commented on Jul 16, 2024

    @moogoos

    Same problem for me
    Ubuntu 24.04
    NVIDIA-SMI 555.58.02
    Driver Version: 555.58.02
    CUDA Version: 12.5
    ffmpeg version 6.1.1-3ubuntu5 Copyright (c) 2000-2023 the FFmpeg developers
    built with gcc 13 (Ubuntu 13.2.0-23ubuntu3)

  4. ramhaidar commented on Sep 30, 2026

    @ramhaidar
    Collaborator

    CUDA_ERROR_OUT_OF_MEMORY means CUDA couldn't allocate. That's not a session-limit failure. So the test result tells you nothing about whether the patch works.

    The tester fires off multiple simultaneous sessions, but it can't tell the difference between hitting the session limit, running out of GPU memory, and some other encoding failure. Those all look the same from the output.

    What it should do: use less GPU memory, shorter and lower-resolution workloads, confirm every requested session actually initializes and finishes, separate NVENC session-limit errors from CUDA allocation failures, and print PASS/FAIL/INCONCLUSIVE instead of making you read FFmpeg output.

    Related: #791, another limitation in the same procedure.

    Keeping this open. Contributions and reproducible results welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions