Use big cfg.g_w in ConfigResizeChangeThreadCount
authorWan-Teh Chang <wtc@google.com>
Sun, 1 Oct 2023 02:45:35 +0000 (19:45 -0700)
committerWan-Teh Chang <wtc@google.com>
Mon, 2 Oct 2023 20:55:16 +0000 (13:55 -0700)
commitb729684b059d48b6bac0750045acbe6a4a9e9a6b
treef37c3bacfa83fad67e287eb73e63ab055e518be9
parent95cb5eae70d2793d3d05413613aca96042261f26
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
test/encode_api_test.cc