While "normal" testing seems OK I've found a way to =
rarely get gstreamer to
fail to allocate a buffer.

ERROR vaapi gstvaapiencoder.c:341:gst_vaapi_encoder_put_frame: failed to
allocate coded buffer
ERROR vaapiencode gstvaapiencode.c:558:gst_vaapiencode_handle_frame: failed=
 to
encode frame 559 (status -2)

This was a mean test - transcoding a 1080p file repeatedly with a couple of
scripts running that after random 1 to 20sec sleeps turn cpu/gpu from perf =
to
auto.

As long as nothing else is happening the results are good, but if I say run=
 an
opengl demo like Unigine Valley as well there's a chance that I get the abo=
ve
fail on say 1 out of 80 runs where a run is transcoding a 120 sec 24 fps
sample.

I can reproduce this with cbr, vbr or cqp and single instance - so maybe it
should get its own bug ....

Though using extreme tests to reproduce I initially noticed this without
running gl as such =3D only glamor scrolling xterm very fast as I had a loa=
d of
printfs in the code.