Closed aaronhudon closed 1 year ago
Thank you for filing this issue. In order for us to investigate this issue, please provide a minimalistic repro project that illustrates the problem.
@mkArtakMSFT to reproduce this, you will need a production-level ASP MVC5 system running in Azure, and enable Optimization Insights.
Make sure your system has a decent amount of traffic, and the pages it services uses @Url.Action
numerous times in a Razor page.
Without a reliable repro we won't be able to investigate this further. Also, we're focusing only on critical bugs and security fixes on this repo. We won't be able to address issues which are "nice to have". I refer to it this way, because that code hasn't been updated for many years and we haven't seen major concerns with it.
Using nuget 5.2.7
I know this code base is getting long in the tooth...but so am I, and here we are.
I have enabled Optimization Insights on a fairly high-traffic SaaS system with the above mentioned version. The largest pain point I am seeing from Optimization Insights is the condition that
UrlHelper.Action
is chewing up memory.Short of upgrading (which will be no small feat), or coming up with my own routing mechanism....any ideas, any hope?
Output from Opt Insights: