-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
Missing function: schedule_background_exec #16516
Comments
If you have a small repro, could you post it? There's a good chance this will just go away on its own when we update Mono, but it would be nice to check. |
Sounds good. You can reproduce this by replacing RepeatString in MonoSanityClient: var result = new StringBuilder();
for (var j = 0; j < 10000; j++)
{
var innerResult = new StringBuilder();
for (var i = 0; i < count; i++)
{
result.Append(str + j.ToString());
}
}
return result.ToString(); then if you click the relevant Go button once it works, a second time it fails. It's not just the repeat, if you replace the parameter "Hello" with something longer, e.g. "Missing function: schedule_background_exec" it fails within one call. |
As predicted, this problem went away on its own when I updated Mono. I guess they fixed it by adding this line: https://github.com/aspnet/Blazor/blob/1d79e72167ff22cead24ff16b0ace79c18a77d82/src/mono/incoming/library_mono.js#L14 Thanks again @cgravill for posting the really clear repro :) |
Thanks @SteveSandersonMS that's excellent and much appreciated. The update works for our actual code too - compilers with bigger code examples. It also worked with some of our optimisation code based on Math.NET which is pretty impressive! |
Great to see more activity on this!
I tried out with some .net code we like to run client-side and was pleasantly surprised to see that it worked without change. However, when I run the same function a few times I get a warning schedule_background_exec followed by an abort:
Is this likely to be a memory issue? I can find schedule_background_exec in the mono source but it looks like the version in Blazor (library_mono.js) is older: mono/mono@d5ebaad#diff-342565351091ae5f9ac0212cc298e1f5
The text was updated successfully, but these errors were encountered: