-
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][Threading] garray.c:226: assertion 'array != NULL' failed
#70572
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsDescriptionAfter a while, when using threads, the runtime fails with multiple internal errors. Reproduction StepsGiven a Wasm Threads enabled runtime, and the following code: static void Main()
{
Console.WriteLine($"Runtime Version: " + RuntimeInformation.FrameworkDescription);
Console.WriteLine($"Runtime Mode: " + runtimeMode);
Console.WriteLine($"TID: {Thread.CurrentThread.ManagedThreadId}");
Bug01();
}
private static void Bug01()
{
Timer t = new Timer(_ =>
{
Log($"Before GC");
GC.Collect();
Log($"After GC");
});
t.Change(5000, 0);
Log($"-> Bug01");
Task.Run(async () =>
{
var sw = Stopwatch.StartNew();
Log($"Before 2000ms delay");
await Task.Delay(2000);
Log($"After delay {sw.ElapsedMilliseconds}");
});
Log($"<- Bug01");
void Log(string message) => Console.WriteLine($"[TID:{Thread.CurrentThread.ManagedThreadId}] {message}");
} Expected behaviorThe runtime does not fail. Actual behaviorAfter about 30 second, the following errors appear:
Regression?no Known WorkaroundsNone ConfigurationOther informationNo response
|
Description
After a while, when using threads, the runtime fails with multiple internal errors.
Reproduction Steps
Given a Wasm Threads enabled runtime, and the following code:
Expected behavior
The runtime does not fail.
Actual behavior
After about 30 second, the following errors appear:
Regression?
no
Known Workarounds
None
Configuration
be4d292
Other information
No response
The text was updated successfully, but these errors were encountered: