Skip to content

DbConnectionPool shouldn't capture AsyncLocals into its Timer #24528

@benaadams

Description

@benaadams

Causing those AsyncLocal values to live forever

As seen in https://github.com/dotnet/corefx/issues/25477#issuecomment-346866897

For ASP.NET Core can capture logging scope, HttpContext, ConcurrentBag items, Authentication (example https://github.com/dotnet/corefx/issues/25477#issuecomment-346866897); other state etc

Metadata

Metadata

Assignees

Labels

area-System.Data.SqlClientenhancementProduct code improvement that does NOT require public API changes/additions

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions