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.

Sign up for GitHub

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

Jump to bottom

Properly use SizeRef in MemoryCache once it is exposed in CoreClr #1427

Open
KKhurin opened this issue Jan 23, 2018 · 2 comments
Open

Properly use SizeRef in MemoryCache once it is exposed in CoreClr #1427

KKhurin opened this issue Jan 23, 2018 · 2 comments
Assignees
@KKhurin
Labels
area-System.Runtime.Caching backlog-cleanup-candidate An inactive issue that has been marked for automated closure. blocked Issue/PR is blocked on something - see comments enhancement Product code improvement that does NOT require public API changes/additions no-recent-activity
Milestone
Future

Comments

@KKhurin
Copy link
Member

KKhurin commented Jan 23, 2018

Once https://github.com/dotnet/coreclr/issues/14561 is fixed MemoryCache should start using it.
@KKhurin KKhurin self-assigned this Jan 23, 2018
@StephenBonikowsky
Copy link
Member

Dependent on the API exposure in CoreClr (linked in description).

@StephenBonikowsky StephenBonikowsky transferred this issue from dotnet/corefx Jan 8, 2020
@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added the untriaged New issue has not been triaged by the area owner label Jan 8, 2020
@StephenBonikowsky StephenBonikowsky added this to the Future milestone Jan 8, 2020
@StephenBonikowsky StephenBonikowsky added area-System.Runtime.Caching and removed untriaged New issue has not been triaged by the area owner labels Jan 8, 2020
@StephenBonikowsky StephenBonikowsky added enhancement Product code improvement that does NOT require public API changes/additions blocked Issue/PR is blocked on something - see comments labels Feb 28, 2020
@StephenBonikowsky StephenBonikowsky removed this from the Future milestone Mar 5, 2020
@HongGit HongGit mentioned this issue Apr 30, 2020
Closed
@HongGit HongGit added this to the Future milestone Jun 18, 2020
MichalStrehovsky pushed a commit to MichalStrehovsky/runtime that referenced this issue Dec 9, 2021
@kant2002
Add access violation location in ASM (dotnet#1427)
eb76479 
* Add access violation location in ASM
That location used in `InInterfaceDispatchHelper` to check for possible NRE
See dotnet#1424

* Use red-zoning for r1 and r2 registers.
@dotnet-policy-service Dotnet Policy Service
Copy link
Contributor

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.

@dotnet-policy-service dotnet-policy-service bot added backlog-cleanup-candidate An inactive issue that has been marked for automated closure. no-recent-activity labels Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@KKhurin KKhurin

Labels
area-System.Runtime.Caching backlog-cleanup-candidate An inactive issue that has been marked for automated closure. blocked Issue/PR is blocked on something - see comments enhancement Product code improvement that does NOT require public API changes/additions no-recent-activity
Projects
None yet
Milestone
Future
Development

No branches or pull requests
4 participants
@KKhurin @StephenBonikowsky @HongGit @Dotnet-GitSync-Bot