Skip to content
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

Don't dispose timers if we're in our UnhandledException handler. #104829

Conversation

StephenMolloy
Copy link
Member

  • Description -
    Timer was updated in 5.0 to improve performance, but is prone to deadlocks when manipulated in an unhandled exception handler. Which MemoryCache does. And MemoryCache is probably more likely to witness unhandled exceptions like OOM than typical code.
  • Customer Impact - The deadlock is preventing a first-party team (Exchange/Substrate) from migrating to .Net 6 and 8.
  • Regression? - From NetFx, yes.
  • Risk Low.

Original Issue: #64115 (and #102666)
.Net 9.0 PR: #103937

System.Runtime.Caching is an OOB package that ships alongside the runtime.

@carlossanlop
Copy link
Member

Friendly reminder that today Monday July 15th is Code Complete day at 4pm PT, which is the deadline to get this included in the August Release.

@StephenMolloy StephenMolloy changed the base branch from release/6.0 to release/6.0-staging July 16, 2024 16:19
@StephenMolloy StephenMolloy force-pushed the bp6_64115_Memcache-UnhandledEx-Timer-Deadlock branch from ac50069 to 294f2a3 Compare July 16, 2024 18:29
@StephenMolloy
Copy link
Member Author

Closed in favor of #106220

@github-actions github-actions bot locked and limited conversation to collaborators Sep 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-System.Runtime.Caching Servicing-consider Issue for next servicing release review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants