-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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][Profiled AOT] Error: TaskT_TransitionToFinal_AlreadyCompleted #77122
Comments
Tagging subscribers to this area: @dotnet/ncl Issue DetailsDescriptionWhen running the code below, the app crashes when built with an AOT profile. When running with the interpreter, or without a profile, the app runs properly. Reproduction StepsWhen running the following code using profiled AOT: public static class Program
{
static async Task Main(string[] args)
{
await Fetch();
}
private static async Task Fetch()
{
try
{
var client = new System.Net.Http.HttpClient()
{
DefaultRequestHeaders = { { "origin", "WindowsCalculator" } }
};
var r = await client.GetAsync(new Uri("https://cors-anywhere.herokuapp.com/https://www.google.com/images/branding/googlelogo/1x/googlelogo_light_color_272x92dp.png"));
Console.WriteLine($"Got Response");
var c = await r.Content.ReadAsByteArrayAsync();
Console.WriteLine($"Got {c.Length} bytes");
}
catch (Exception e)
{
Console.WriteLine($"Failure: " + e);
}
}
} Profile: aot.zip Expected behaviorNo crash, bytes are reported. Actual behavior
Regression?Yes, .NET 6 does not have this issue. Known WorkaroundsNo response ConfigurationTested on both: Other informationNo response
|
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsDescriptionWhen running the code below, the app crashes when built with an AOT profile. When running with the interpreter, or without a profile, the app runs properly. Reproduction StepsWhen running the following code using profiled AOT: public static class Program
{
static async Task Main(string[] args)
{
await Fetch();
}
private static async Task Fetch()
{
try
{
var client = new System.Net.Http.HttpClient()
{
DefaultRequestHeaders = { { "origin", "WindowsCalculator" } }
};
var r = await client.GetAsync(new Uri("https://cors-anywhere.herokuapp.com/https://www.google.com/images/branding/googlelogo/1x/googlelogo_light_color_272x92dp.png"));
Console.WriteLine($"Got Response");
var c = await r.Content.ReadAsByteArrayAsync();
Console.WriteLine($"Got {c.Length} bytes");
}
catch (Exception e)
{
Console.WriteLine($"Failure: " + e);
}
}
} Profile: aot.zip Expected behaviorNo crash, bytes are reported. Actual behavior
Regression?Yes, .NET 6 does not have this issue. Known WorkaroundsNo response ConfigurationTested on both: Other informationNo response
|
@vargaz using profile filtering, I've narrowed the issue down to it being one of those AOTed:
Still a large number of methods, but better than nothing. |
Also, using net8, the error comes up as follow:
|
Would it be possible to create a testcase which uses the normal .net build ? |
I'm not able to reproduce with a normal .NET build, there must be an option that's doing something differently. The exception above being raise is hiding this exception:
|
Here's a repro with the vanilla .NET tooling. 77122-test-aot.zip The issue only happens when |
cc @kotlarmilos |
is this still a problem ? |
This issue has been marked |
Description
When running the code below, the app crashes when built with an AOT profile. When running with the interpreter, or without a profile, the app runs properly.
Reproduction Steps
When running the following code using profiled AOT:
Profile: aot.zip
Full repro: https://github.com/jeromelaban/Wasm.Samples/tree/master/AotIssueMismatch77122
Expected behavior
No crash, bytes are reported.
Actual behavior
Regression?
Yes, .NET 6 does not have this issue.
Known Workarounds
No response
Configuration
Tested on both:
main: 9567f27
release/7.0: cd2d837
Other information
No response
The text was updated successfully, but these errors were encountered: