New Chrome_RenderWidgetHostHWND showing up

34 views
Skip to first unread message

Don Schmitt

unread,
Mar 5, 2026, 5:04:34 PM (9 days ago) Mar 5
to Chromium-dev
We're encountering some issues due to the creation of 1-2 new Chrome_RenderWidgetHostHWNDs that weren't previously being created. They appear to be 0 or 60 pixels in height, so they do not map to the tab's client window like the normal RWHW.

We do have a workaround for the issue this is causing, but I'm trying to find the root source of these new RWHWs to reproduce this reliably.

The issue being seen by users is very sporadic, so I suspect perhaps an experimental feature is at play?  Does anyone have insights into what is happening here?

Thanks!

Joe Mason

unread,
Mar 5, 2026, 6:47:50 PM (8 days ago) Mar 5
to donc...@gmail.com, Chromium-dev
There's a script at https://source.chromium.org/chromium/chromium/src/+/main:tools/variations/bisect_variations.py that will run Chrome with different combinations of experiments, to narrow down which one is causing the problem.

Please file a bug at crbug.com and include the "Active variations" list from chrome://version in a browser that shows the problem. Including the results of bisect_variations.py would be even better.


--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAM7AMp%2Bu9WZLzxCN5zJP%3Dwx7_kpopa-RFeYM-cUihj4Xyt7E-g%40mail.gmail.com.

Don Schmitt

unread,
Mar 5, 2026, 11:58:55 PM (8 days ago) Mar 5
to Joe Mason, Chromium-dev
Wow, thanks for the quick responses, and that bisect_variations.py is very cool!   I entered the bug here: https://issues.chromium.org/issues/490137353

FYI the result of the bisect is below, which seems correct because the new render widget that was messing us up seems to be hovering over the Omnibox:

Bisecting succeeded: --force-fieldtrials=*OmniboxNext_Desktop/EnabledInlineWithoutChips_V6/ --force-fieldtrial-params=OmniboxNext_Desktop.EnabledInlineWithoutChips_V6:AddContextButtonVariant/inline/Omnibox_AddContextButtonVariant/inline/Omnibox_ShowLensSearchChip/false/Omnibox_ShowRecentTabChip/false/Omnibox_ShowSmartCompose/false/ShowLensSearchChip/false/ShowRecentTabChip/false/ShowSmartCompose/false --enable-features=WebUIOmniboxAimPopup<OmniboxNext_Desktop,WebUIOmniboxPopup<OmniboxNext_Desktop


Reply all
Reply to author
Forward
0 new messages