New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 769722 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

elm: failed VEA unittest, bitrate is much less than a requested bitrate.

Project Member Reported by hiroh@chromium.org, Sep 28 2017

Issue description

VEA unittest are failed on elm for MidStreamParamSwitchBitrate/VideoEncodeAcceleratorTest.TestSimpleEncode/0 and MultipleEncoders/VideoEncodeAcceleratorTest.TestSimpleEncode/1.

The ChromeOS version is R63.9983.0.0.
Because these test cases doesn't run by video_VideoEncodeAccelerator, video_VideoEncodeAccelerator is passed.

# ./video_encode_accelerator_unittest --test_stream_data=crowd1080-96f60dd6ff87ba8b129301a0f36efc58.yuv:1920:1080:1:crowd.out:4000000 --ozone-platform=gbm
[ RUN      ] MidStreamParamSwitchBitrate/VideoEncodeAcceleratorTest.TestSimpleEncode/0
[0928/062555.897364:INFO:video_encode_accelerator_unittest.cc(476)] Measured encoder FPS: 68.284

../../../../../chromeos-cache/distfiles/target/chrome-src/src/media/gpu/video_encode_accelerator_unittest.cc:1949: Failure
The difference between bitrate and current_requested_bitrate_ is 3998127, which exceeds kBitrateTolerance * current_requested_bitrate_, where
bitrate evaluates to 4001873,
current_requested_bitrate_ evaluates to 8000000, and
kBitrateTolerance * current_requested_bitrate_ evaluates to 800000.
[  FAILED  ] MidStreamParamSwitchBitrate/VideoEncodeAcceleratorTest.TestSimpleEncode/0, where GetParam() = (1, false, 0, true, false, true, false, false, false) (4421 ms)
[ RUN      ] MultipleEncoders/VideoEncodeAcceleratorTest.TestSimpleEncode/1
[0928/062618.117684:INFO:video_encode_accelerator_unittest.cc(476)] Measured encoder FPS: 22.708

../../../../../chromeos-cache/distfiles/target/chrome-src/src/media/gpu/video_encode_accelerator_unittest.cc:1949: Failure
The difference between bitrate and current_requested_bitrate_ is 3998127, which exceeds kBitrateTolerance * current_requested_bitrate_, where
bitrate evaluates to 4001873,
current_requested_bitrate_ evaluates to 8000000, and
kBitrateTolerance * current_requested_bitrate_ evaluates to 800000.
[0928/062618.132278:INFO:video_encode_accelerator_unittest.cc(476)] Measured encoder FPS: 22.682

../../../../../chromeos-cache/distfiles/target/chrome-src/src/media/gpu/video_encode_accelerator_unittest.cc:1949: Failure
The difference between bitrate and current_requested_bitrate_ is 3998127, which exceeds kBitrateTolerance * current_requested_bitrate_, where
bitrate evaluates to 4001873,
current_requested_bitrate_ evaluates to 8000000, and
kBitrateTolerance * current_requested_bitrate_ evaluates to 800000.
[  FAILED  ] MultipleEncoders/VideoEncodeAcceleratorTest.TestSimpleEncode/1, where GetParam() = (3, false, 0, true, false, true, false, false, false) (13376 ms)
 

Comment 1 by hiroh@chromium.org, Sep 29 2017

I confirmed VDA unittest (Chrome R63.0.3203.0) was failed too.
I will try finding a good point today.

Comment 2 Deleted

Comment 3 by hiroh@chromium.org, Sep 29 2017

I confirmed the same test cases were failed on ChromeOS R57-9202.64.0.
That is the Chrome OS installed on elm when elm was launched.
This shows this bug has happened since elm was launched and this is not regression.
The bug failure reason seems due to MTK hardware problem, not Chrome and ChromeOS.
It doesn't compute bitrate correctly.

Cc: owenlin@chromium.org
Owner: drinkcat@chromium.org
It sounds like a partner issue.

Hi Nicolas,
Please help to assign this issue to the right owner in mediatek. 
Cc: drinkcat@chromium.org
Owner: wuchengli@chromium.org
Assuming this is not a graphics issue, passing back to wuchengli.
Labels: -videoshortlist
Labels: -Pri-1 Pri-3
Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".

Sign in to add a comment