Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Size regression in Blazor WASM apps
See original GitHub issueLooking at https://aka.ms/dotnetperfstatus, there is a 140KB size regression in the default Blazor WASM app size between the following commits:
https://github.com/dotnet/runtime/compare/6b8326997...06228c1087
SOD - New Blazor Template - Publish
SOD - New Blazor Template - Publish - AOT
We should investigate what change caused this size regression and if there is anything that can be done.
From looking at the charts, some of it comes from System.Private.CoreLib:
Before
After
But the biggest file that added here is System.Linq.Expressions.dll. It isn’t in the Before, but in the After it is over 100KB itself:
After
Maybe a new ASP.NET change now brings in Linq.Expressions by default? cc @SteveSandersonMS @captainsafia
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yep, great - thanks. Rolling this change back does feel right. Maybe activation-by-default could come back in the future if the underlying implementation is updated, but it’s not a big loss to tell customers they can do this themselves in user code.
It’s really great that we’re able to detect this kind of thing systematically. Thanks for letting us know, @eerhardt!