From: Wan-Teh Chang <wtc@google.com>
Date: Sun, 1 Oct 2023 02:45:35 +0000 (-0700)
Subject: Use big cfg.g_w in ConfigResizeChangeThreadCount
X-Git-Tag: accepted/tizen/7.0/unified/20240521.012539~1^2~74
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=b729684b059d48b6bac0750045acbe6a4a9e9a6b;p=platform%2Fupstream%2Flibvpx.git

Use big cfg.g_w in ConfigResizeChangeThreadCount

vp8cx_create_encoder_threads() caps the thread count at
(cm->mb_cols / cpi->mt_sync_range) - 1. If cfg.g_w is 16, cm->mb_cols is
only 1 (see vp8_alloc_frame_buffers: mb_cols = width >> 4), so we won't
be using multiple threads. To reproduce bug chromium:1486441, the test
just needs to increase cfg.g_h sufficiently.

Bug: chromium:1486441
Change-Id: Ie6b2da2e31cfa1717a481f55eebc8c875db94d87
---

diff --git a/test/encode_api_test.cc b/test/encode_api_test.cc
index f1c98b2..6b22feb 100644
--- a/test/encode_api_test.cc
+++ b/test/encode_api_test.cc
@@ -396,7 +396,7 @@ TEST(EncodeAPI, ConfigResizeChangeThreadCount) {
       EXPECT_EQ(vpx_codec_enc_config_set(&enc.ctx, &cfg), VPX_CODEC_OK)
           << vpx_codec_error_detail(&enc.ctx);
 
-      cfg.g_w = 16;
+      cfg.g_w = 1000;
       cfg.g_h = 720;
 
       for (const auto threads : { 1, 4, 8, 6, 2, 1 }) {