-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[wasm] System.Net.Http.BrowserHttpHandler.SendAsync() throws NRE #53872
Comments
Tagging subscribers to this area: @dotnet/ncl Issue DetailsIn unit test
|
- move tests to inner loop - more granular ActiveIssue dotnet#53592 for lack of TRACE - more granular ActiveIssue dotnet#53591 for content on GET/HEAD - more granular ActiveIssue dotnet#53874 for HttpRequestMessage.Headers.Host - more granular ActiveIssue dotnet#53872 for NPE on System.Net.Http.BrowserHttpHandler - fix HTTP vs HTTPS test configuration `Http2SecureRemoteEchoServer` - include echo middleware in xharness server - include middleware in Helix correlation payload
Looking at the test I don't see an obvious reason it should fail like this. Is this failing on all browser lanes? There was some work done allow trimming more of the header logic out and if these tests weren't running they may have regressed. |
- move tests to inner loop - include echo middleware in xharness server - improve doc - more granular ActiveIssue #53592 for lack of TRACE - more granular ActiveIssue #53591 for content on GET/HEAD - more granular ActiveIssue #53874 for HttpRequestMessage.Headers.Host - more granular ActiveIssue #53872 for NPE on System.Net.Http.BrowserHttpHandler - more granular ActiveIssue #53876 - include middleware in Helix correlation payload
Here is example of the failure on CI This time different test and on ubuntu, not windows. Maybe race condition ? |
Yes second CI run on the same code as above is green. |
Another locally
|
|
Repro at pavelsavara@a2b0a7b#diff-66ce677ded58c3a6a0639d321f4460bb0b2c4bcaeb3216ff3db4381937365bd8 It fails randomly with I think JSObject is returned as null from some of the marshaling calls. |
Most likely explanation is a GC issue. I think if it were memory corruption in the runtime (which has been known to happen, but hasn't - afaik - been seen recently) it wouldn't just be consistently producing NREs, other bad stuff would be happening. |
Very simple steps to reproduce here https://github.com/dotnet/runtime/pull/54453/files
|
looks similar to
|
In unit test
System.Net.Http.Functional.Tests.HttpClientHandler_RemoteServerTest.GetAsync_RequestHeadersAddCustomHeaders_HeaderAndEmptyValueSent(remoteServer: (BaseUri: https://127.0.0.1:61813/, HttpVersion: 1.1)
on WASM and browser.This is not network related issue, it could be reproduced without
BrowserHttpHandler
see https://github.com/dotnet/runtime/pull/54453/filesThe text was updated successfully, but these errors were encountered: