-
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] Reduce amount of exception filtering in code reached from Blazor template #50281
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsException filtering on wasm is slow, because we cannot unwind stack and thus need to switch from AOT to interpreter for parts of the code. Try to reduce amount of exception filtering in parts of our libraries, which are used in Blazor template. In the linked assemblies we have currently 9 filter blocks:
|
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 this area: @CoffeeFlux Issue DetailsException filtering on wasm is slow, because we cannot unwind stack and thus need to switch from AOT to interpreter for parts of the code. Try to reduce amount of exception filtering in parts of our libraries, which are used in Blazor template. In the linked assemblies we have currently 9 filter blocks:
|
This was discussed here: |
@radekdoulik, do we still plan to remove the filters in the light of @jkotas and @stephentoub arguments? |
Exception filtering on wasm is slow, because we cannot unwind stack and thus need to switch from AOT to interpreter for parts of the code.
Try to reduce amount of exception filtering in parts of our libraries, which are used in Blazor template. In the linked assemblies we have currently 9 filter blocks:
The text was updated successfully, but these errors were encountered: