PSA: HTTP/2 XHR requests stall in Chrome/Chromium

[niftylettuce]

See https://bugs.chromium.org/p/chromium/issues/detail?id=1045328#c_ts1590985341. This is a core bug and dates back to at least January. Affects all versions of Node.js as far I can tell, as this bug is directly related to Chromium. Posting this here if anyone encounters it or is able to reproduce. I can easily reproduce with the open source codebase I mentioned in the Chromium bug report.

[niftylettuce]

The Chromium team has marked this bug as internally viewable to Google members only. I will update here as I find more information.

[niftylettuce]

We just made this issue publicly viewable again @ https://bugs.chromium.org/p/chromium/issues/detail?id=1045328#c57.

I will offer a $200 bounty or matching donation to the charity of your choice to whoever determines issue.

Hope you can lend a hand here! Some of the Chromium team is stumped on this one!

[niftylettuce]

cc @indutny @jasnell @bnoordhuis

[niftylettuce]

See the file "output.txt" I uploaded in comment #60 https://bugs.chromium.org/p/chromium/issues/detail?id=1045328#c60 for output from the Node.js process showing the connection is stalled for 120 seconds and then destroyed.

[mcollina]

There are a few of these that are similar... a PR to fix it would be very handy. No one know why it happens.

cc @jasnell

[niftylettuce]

@mcollina doesn't #33875 fix it?

[mcollina]

I don’t know if it fixes this issue. Or is it the same issue? Have you tested it?

[niftylettuce]

Seems to me like the same issue, I'm not sure how to test to see if it resolves. But all the source code is public in my demo.

[Textras]

@niftylettuce ever find resolution?

[niftylettuce]

Yes, upgrade to Node v14+ per #33875. This was also backported to older