[BUG] Main Chrome.exe process appeared Deadlocked after start. (may be caused by code from progwrp.dll)

[IDA-RE-things]

Symptoms and Bug Description:
When I started the browser (may be after crash, dont know),
After 2 windows with tabs starts opened, The browser appears deadlocked, and dont respond to any user actions. No content inside tabs displayed. All threads are in Wait state. And no CPU activity.

Additional info:
I'm using --process-per-site switch.

(As we can see from screenshots of thread states and callstacks, it may be caused by code inside progwrp.dll: Implementation_SleepConditionVariableSRW. But may be no)

To Reproduce:
Can't do such..

Screenshots:

Config:

• OS: XP 32-bit
• https://github.com/win32ss/supermium/releases/tag/v122-hf
• chrome.dll: latest available: (17.03.2024) : https://github.com/win32ss/supermium/releases/download/v122-dbg/122_new_pdb_32.7z
  progwrp.dll: latest 1.1.0.5002 (08.04.2024) : https://github.com/win32ss/supermium/files/14902003/progwrp_32.zip

[IDA-RE-things]

UPD: the main thread in main Chrome.exe process now seems working (not waiting at least)
Its waiting for WM_ messages in
\base\message_loop\message_pump_win.cc
MessagePumpForUI::WaitForWork();
Then it do something, and returns here.

But renderer processes are still not refreshing anything.(any tabs contents can'be displayed).
I can create new empty tab. But it can't render URL's I entered.
Now 7 renderer processes (was 3).
So it can't communicate with renderer processes ?
Dont know whats happened here, and will restart the browser.