Update OutOfMemoryException test by eduardo-vp · Pull Request #130146 · dotnet/runtime

eduardo-vp · 2026-07-02T23:06:54Z

I think the test is not GC stress compatible. The small allocations loops finish earlier than expected because of the allocations done by the GC and all the final loop can just finish instead of OOMing.

runtime/src/tests/baseservices/exceptions/OutOfMemoryException/OutOfMemoryException.cs

Lines 32 to 44 in 57fc9dc

if(args.Length>0&&args[0]==AllocateSmallArg)
{
// Pre-allocate a flat array for storage.
object[]storage=newobject[8192];
intidx=0;
// We expect ~2048 iterations in the first loop and ~64 iterations in the second.
try{while(idx<storage.Length)storage[idx++]=GC.AllocateArray<byte>(16*1024,pinned:true);}catch(OutOfMemoryException){}
try{while(idx<storage.Length)storage[idx++]=GC.AllocateArray<byte>(256,pinned:true);}catch(OutOfMemoryException){}
// < 280 bytes free.
// Use the smallest possible allocation to exhaust the last scraps.
while(idx<storage.Length)storage[idx++]=GC.AllocateArray<byte>(1,pinned:true);
returnFail;
}

Fixes#129159.

dotnet-policy-service · 2026-07-02T23:08:00Z

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

Copilot

Pull request overview

This PR updates the OutOfMemoryException test project configuration to avoid running the test under GCStress, where its OOM timing/behavior is unstable and can lead to non-representative failures.

Changes:

Mark the test as GCStress-incompatible via GCStressIncompatible=true.
Add an explanatory comment in the project file documenting why GCStress makes this test unreliable.

I think the test is not GC stress compatible. The small allocations loops finish earlier than expected because of the allocations done by the GC and all the final loop can just finish instead of OOMing. https://github.com/dotnet/runtime/blob/57fc9dc8acd841ecffb733faf8def2cd96fadfd0/src/tests/baseservices/exceptions/OutOfMemoryException/OutOfMemoryException.cs#L32-L44Fixes#129159. Co-authored-by: Eduardo Velarde <evelardepola@microsoft.com>

eduardo-vp · 2026-07-02T23:06:54Z

I think the test is not GC stress compatible. The small allocations loops finish earlier than expected because of the allocations done by the GC and all the final loop can just finish instead of OOMing.

runtime/src/tests/baseservices/exceptions/OutOfMemoryException/OutOfMemoryException.cs

Lines 32 to 44 in 57fc9dc

if(args.Length>0&&args[0]==AllocateSmallArg)
{
// Pre-allocate a flat array for storage.
object[]storage=newobject[8192];
intidx=0;
// We expect ~2048 iterations in the first loop and ~64 iterations in the second.
try{while(idx<storage.Length)storage[idx++]=GC.AllocateArray<byte>(16*1024,pinned:true);}catch(OutOfMemoryException){}
try{while(idx<storage.Length)storage[idx++]=GC.AllocateArray<byte>(256,pinned:true);}catch(OutOfMemoryException){}
// < 280 bytes free.
// Use the smallest possible allocation to exhaust the last scraps.
while(idx<storage.Length)storage[idx++]=GC.AllocateArray<byte>(1,pinned:true);
returnFail;
}

Fixes#129159.

dotnet-policy-service · 2026-07-02T23:08:00Z

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

Copilot

Pull request overview

This PR updates the OutOfMemoryException test project configuration to avoid running the test under GCStress, where its OOM timing/behavior is unstable and can lead to non-representative failures.

Changes:

Mark the test as GCStress-incompatible via GCStressIncompatible=true.
Add an explanatory comment in the project file documenting why GCStress makes this test unreliable.

I think the test is not GC stress compatible. The small allocations loops finish earlier than expected because of the allocations done by the GC and all the final loop can just finish instead of OOMing. https://github.com/dotnet/runtime/blob/57fc9dc8acd841ecffb733faf8def2cd96fadfd0/src/tests/baseservices/exceptions/OutOfMemoryException/OutOfMemoryException.cs#L32-L44Fixes#129159. Co-authored-by: Eduardo Velarde <evelardepola@microsoft.com>

eduardo-vp · 2026-07-02T23:06:54Z

I think the test is not GC stress compatible. The small allocations loops finish earlier than expected because of the allocations done by the GC and all the final loop can just finish instead of OOMing.

runtime/src/tests/baseservices/exceptions/OutOfMemoryException/OutOfMemoryException.cs

Lines 32 to 44 in 57fc9dc

if(args.Length>0&&args[0]==AllocateSmallArg)
{
// Pre-allocate a flat array for storage.
object[]storage=newobject[8192];
intidx=0;
// We expect ~2048 iterations in the first loop and ~64 iterations in the second.
try{while(idx<storage.Length)storage[idx++]=GC.AllocateArray<byte>(16*1024,pinned:true);}catch(OutOfMemoryException){}
try{while(idx<storage.Length)storage[idx++]=GC.AllocateArray<byte>(256,pinned:true);}catch(OutOfMemoryException){}
// < 280 bytes free.
// Use the smallest possible allocation to exhaust the last scraps.
while(idx<storage.Length)storage[idx++]=GC.AllocateArray<byte>(1,pinned:true);
returnFail;
}

Fixes#129159.

dotnet-policy-service · 2026-07-02T23:08:00Z

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

Copilot

Pull request overview

This PR updates the OutOfMemoryException test project configuration to avoid running the test under GCStress, where its OOM timing/behavior is unstable and can lead to non-representative failures.

Changes:

Mark the test as GCStress-incompatible via GCStressIncompatible=true.
Add an explanatory comment in the project file documenting why GCStress makes this test unreliable.

I think the test is not GC stress compatible. The small allocations loops finish earlier than expected because of the allocations done by the GC and all the final loop can just finish instead of OOMing. https://github.com/dotnet/runtime/blob/57fc9dc8acd841ecffb733faf8def2cd96fadfd0/src/tests/baseservices/exceptions/OutOfMemoryException/OutOfMemoryException.cs#L32-L44Fixes#129159. Co-authored-by: Eduardo Velarde <evelardepola@microsoft.com>

eduardo-vp · 2026-07-02T23:06:54Z

I think the test is not GC stress compatible. The small allocations loops finish earlier than expected because of the allocations done by the GC and all the final loop can just finish instead of OOMing.

runtime/src/tests/baseservices/exceptions/OutOfMemoryException/OutOfMemoryException.cs

Lines 32 to 44 in 57fc9dc

if(args.Length>0&&args[0]==AllocateSmallArg)
{
// Pre-allocate a flat array for storage.
object[]storage=newobject[8192];
intidx=0;
// We expect ~2048 iterations in the first loop and ~64 iterations in the second.
try{while(idx<storage.Length)storage[idx++]=GC.AllocateArray<byte>(16*1024,pinned:true);}catch(OutOfMemoryException){}
try{while(idx<storage.Length)storage[idx++]=GC.AllocateArray<byte>(256,pinned:true);}catch(OutOfMemoryException){}
// < 280 bytes free.
// Use the smallest possible allocation to exhaust the last scraps.
while(idx<storage.Length)storage[idx++]=GC.AllocateArray<byte>(1,pinned:true);
returnFail;
}

Fixes#129159.

dotnet-policy-service · 2026-07-02T23:08:00Z

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

Copilot

Pull request overview

This PR updates the OutOfMemoryException test project configuration to avoid running the test under GCStress, where its OOM timing/behavior is unstable and can lead to non-representative failures.

Changes:

Mark the test as GCStress-incompatible via GCStressIncompatible=true.
Add an explanatory comment in the project file documenting why GCStress makes this test unreliable.

I think the test is not GC stress compatible. The small allocations loops finish earlier than expected because of the allocations done by the GC and all the final loop can just finish instead of OOMing. https://github.com/dotnet/runtime/blob/57fc9dc8acd841ecffb733faf8def2cd96fadfd0/src/tests/baseservices/exceptions/OutOfMemoryException/OutOfMemoryException.cs#L32-L44Fixes#129159. Co-authored-by: Eduardo Velarde <evelardepola@microsoft.com>

eduardo-vp · 2026-07-02T23:06:54Z

I think the test is not GC stress compatible. The small allocations loops finish earlier than expected because of the allocations done by the GC and all the final loop can just finish instead of OOMing.

runtime/src/tests/baseservices/exceptions/OutOfMemoryException/OutOfMemoryException.cs

Lines 32 to 44 in 57fc9dc

if(args.Length>0&&args[0]==AllocateSmallArg)
{
// Pre-allocate a flat array for storage.
object[]storage=newobject[8192];
intidx=0;
// We expect ~2048 iterations in the first loop and ~64 iterations in the second.
try{while(idx<storage.Length)storage[idx++]=GC.AllocateArray<byte>(16*1024,pinned:true);}catch(OutOfMemoryException){}
try{while(idx<storage.Length)storage[idx++]=GC.AllocateArray<byte>(256,pinned:true);}catch(OutOfMemoryException){}
// < 280 bytes free.
// Use the smallest possible allocation to exhaust the last scraps.
while(idx<storage.Length)storage[idx++]=GC.AllocateArray<byte>(1,pinned:true);
returnFail;
}

Fixes#129159.

dotnet-policy-service · 2026-07-02T23:08:00Z

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

Copilot

Pull request overview

This PR updates the OutOfMemoryException test project configuration to avoid running the test under GCStress, where its OOM timing/behavior is unstable and can lead to non-representative failures.

Changes:

Mark the test as GCStress-incompatible via GCStressIncompatible=true.
Add an explanatory comment in the project file documenting why GCStress makes this test unreliable.

I think the test is not GC stress compatible. The small allocations loops finish earlier than expected because of the allocations done by the GC and all the final loop can just finish instead of OOMing. https://github.com/dotnet/runtime/blob/57fc9dc8acd841ecffb733faf8def2cd96fadfd0/src/tests/baseservices/exceptions/OutOfMemoryException/OutOfMemoryException.cs#L32-L44Fixes#129159. Co-authored-by: Eduardo Velarde <evelardepola@microsoft.com>

eduardo-vp · 2026-07-02T23:06:54Z

I think the test is not GC stress compatible. The small allocations loops finish earlier than expected because of the allocations done by the GC and all the final loop can just finish instead of OOMing.

runtime/src/tests/baseservices/exceptions/OutOfMemoryException/OutOfMemoryException.cs

Lines 32 to 44 in 57fc9dc

if(args.Length>0&&args[0]==AllocateSmallArg)
{
// Pre-allocate a flat array for storage.
object[]storage=newobject[8192];
intidx=0;
// We expect ~2048 iterations in the first loop and ~64 iterations in the second.
try{while(idx<storage.Length)storage[idx++]=GC.AllocateArray<byte>(16*1024,pinned:true);}catch(OutOfMemoryException){}
try{while(idx<storage.Length)storage[idx++]=GC.AllocateArray<byte>(256,pinned:true);}catch(OutOfMemoryException){}
// < 280 bytes free.
// Use the smallest possible allocation to exhaust the last scraps.
while(idx<storage.Length)storage[idx++]=GC.AllocateArray<byte>(1,pinned:true);
returnFail;
}

Fixes#129159.

dotnet-policy-service · 2026-07-02T23:08:00Z

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

Copilot

Pull request overview

This PR updates the OutOfMemoryException test project configuration to avoid running the test under GCStress, where its OOM timing/behavior is unstable and can lead to non-representative failures.

Changes:

Mark the test as GCStress-incompatible via GCStressIncompatible=true.
Add an explanatory comment in the project file documenting why GCStress makes this test unreliable.

I think the test is not GC stress compatible. The small allocations loops finish earlier than expected because of the allocations done by the GC and all the final loop can just finish instead of OOMing. https://github.com/dotnet/runtime/blob/57fc9dc8acd841ecffb733faf8def2cd96fadfd0/src/tests/baseservices/exceptions/OutOfMemoryException/OutOfMemoryException.cs#L32-L44Fixes#129159. Co-authored-by: Eduardo Velarde <evelardepola@microsoft.com>

eduardo-vp · 2026-07-02T23:06:54Z

I think the test is not GC stress compatible. The small allocations loops finish earlier than expected because of the allocations done by the GC and all the final loop can just finish instead of OOMing.

runtime/src/tests/baseservices/exceptions/OutOfMemoryException/OutOfMemoryException.cs

Lines 32 to 44 in 57fc9dc

if(args.Length>0&&args[0]==AllocateSmallArg)
{
// Pre-allocate a flat array for storage.
object[]storage=newobject[8192];
intidx=0;
// We expect ~2048 iterations in the first loop and ~64 iterations in the second.
try{while(idx<storage.Length)storage[idx++]=GC.AllocateArray<byte>(16*1024,pinned:true);}catch(OutOfMemoryException){}
try{while(idx<storage.Length)storage[idx++]=GC.AllocateArray<byte>(256,pinned:true);}catch(OutOfMemoryException){}
// < 280 bytes free.
// Use the smallest possible allocation to exhaust the last scraps.
while(idx<storage.Length)storage[idx++]=GC.AllocateArray<byte>(1,pinned:true);
returnFail;
}

Fixes#129159.

dotnet-policy-service · 2026-07-02T23:08:00Z

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

Copilot

Pull request overview

This PR updates the OutOfMemoryException test project configuration to avoid running the test under GCStress, where its OOM timing/behavior is unstable and can lead to non-representative failures.

Changes:

Mark the test as GCStress-incompatible via GCStressIncompatible=true.
Add an explanatory comment in the project file documenting why GCStress makes this test unreliable.

I think the test is not GC stress compatible. The small allocations loops finish earlier than expected because of the allocations done by the GC and all the final loop can just finish instead of OOMing. https://github.com/dotnet/runtime/blob/57fc9dc8acd841ecffb733faf8def2cd96fadfd0/src/tests/baseservices/exceptions/OutOfMemoryException/OutOfMemoryException.cs#L32-L44Fixes#129159. Co-authored-by: Eduardo Velarde <evelardepola@microsoft.com>

eduardo-vp · 2026-07-02T23:06:54Z

I think the test is not GC stress compatible. The small allocations loops finish earlier than expected because of the allocations done by the GC and all the final loop can just finish instead of OOMing.

runtime/src/tests/baseservices/exceptions/OutOfMemoryException/OutOfMemoryException.cs

Lines 32 to 44 in 57fc9dc

if(args.Length>0&&args[0]==AllocateSmallArg)
{
// Pre-allocate a flat array for storage.
object[]storage=newobject[8192];
intidx=0;
// We expect ~2048 iterations in the first loop and ~64 iterations in the second.
try{while(idx<storage.Length)storage[idx++]=GC.AllocateArray<byte>(16*1024,pinned:true);}catch(OutOfMemoryException){}
try{while(idx<storage.Length)storage[idx++]=GC.AllocateArray<byte>(256,pinned:true);}catch(OutOfMemoryException){}
// < 280 bytes free.
// Use the smallest possible allocation to exhaust the last scraps.
while(idx<storage.Length)storage[idx++]=GC.AllocateArray<byte>(1,pinned:true);
returnFail;
}

Fixes#129159.

dotnet-policy-service · 2026-07-02T23:08:00Z

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

Copilot

Pull request overview

This PR updates the OutOfMemoryException test project configuration to avoid running the test under GCStress, where its OOM timing/behavior is unstable and can lead to non-representative failures.

Changes:

Mark the test as GCStress-incompatible via GCStressIncompatible=true.
Add an explanatory comment in the project file documenting why GCStress makes this test unreliable.

I think the test is not GC stress compatible. The small allocations loops finish earlier than expected because of the allocations done by the GC and all the final loop can just finish instead of OOMing. https://github.com/dotnet/runtime/blob/57fc9dc8acd841ecffb733faf8def2cd96fadfd0/src/tests/baseservices/exceptions/OutOfMemoryException/OutOfMemoryException.cs#L32-L44Fixes#129159. Co-authored-by: Eduardo Velarde <evelardepola@microsoft.com>

Update OutOfMemoryException test
306e235

CopilotAI review requested due to automatic review settings July 2, 2026 23:06

github-actionsBot added the area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI label Jul 2, 2026

dotnet-policy-serviceBot assigned eduardo-vp Jul 2, 2026

Copilotstarted reviewing on behalf of eduardo-vp July 2, 2026 23:07 View session

CopilotAI reviewed Jul 2, 2026
View reviewed changes

eduardo-vp requested a review from JulieLeeMSFT July 2, 2026 23:13

jkotas approved these changes Jul 2, 2026
View reviewed changes

eduardo-vp merged commit e1979b7 into dotnet:mainJul 3, 2026
88 checks passed

dotnet-maestroBot mentioned this pull request Jul 4, 2026
[main] Source code updates from dotnet/runtime dotnet/dotnet#7544
Merged

dotnet-milestone-botBot added this to the 11.0-preview7 milestone Jul 4, 2026

eduardo-vp mentioned this pull request Jul 6, 2026
Assert failure: Consistency check failed: AV in clr at this callstack #129681
Closed

github-actionsBot locked and limited conversation to collaborators Aug 4, 2026

Update OutOfMemoryException test
306e235

CopilotAI review requested due to automatic review settings July 2, 2026 23:06

github-actionsBot added the area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI label Jul 2, 2026

dotnet-policy-serviceBot assigned eduardo-vp Jul 2, 2026

Copilotstarted reviewing on behalf of eduardo-vp July 2, 2026 23:07 View session

CopilotAI reviewed Jul 2, 2026
View reviewed changes

eduardo-vp requested a review from JulieLeeMSFT July 2, 2026 23:13

jkotas approved these changes Jul 2, 2026
View reviewed changes

eduardo-vp merged commit e1979b7 into dotnet:mainJul 3, 2026
88 checks passed

dotnet-maestroBot mentioned this pull request Jul 4, 2026
[main] Source code updates from dotnet/runtime dotnet/dotnet#7544
Merged

dotnet-milestone-botBot added this to the 11.0-preview7 milestone Jul 4, 2026

eduardo-vp mentioned this pull request Jul 6, 2026
Assert failure: Consistency check failed: AV in clr at this callstack #129681
Closed

github-actionsBot locked and limited conversation to collaborators Aug 4, 2026

Update OutOfMemoryException test
306e235

CopilotAI review requested due to automatic review settings July 2, 2026 23:06

github-actionsBot added the area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI label Jul 2, 2026

dotnet-policy-serviceBot assigned eduardo-vp Jul 2, 2026

Copilotstarted reviewing on behalf of eduardo-vp July 2, 2026 23:07 View session

CopilotAI reviewed Jul 2, 2026
View reviewed changes

eduardo-vp requested a review from JulieLeeMSFT July 2, 2026 23:13

jkotas approved these changes Jul 2, 2026
View reviewed changes

eduardo-vp merged commit e1979b7 into dotnet:mainJul 3, 2026
88 checks passed

dotnet-maestroBot mentioned this pull request Jul 4, 2026
[main] Source code updates from dotnet/runtime dotnet/dotnet#7544
Merged

dotnet-milestone-botBot added this to the 11.0-preview7 milestone Jul 4, 2026

eduardo-vp mentioned this pull request Jul 6, 2026
Assert failure: Consistency check failed: AV in clr at this callstack #129681
Closed

github-actionsBot locked and limited conversation to collaborators Aug 4, 2026

Update OutOfMemoryException test
306e235

CopilotAI review requested due to automatic review settings July 2, 2026 23:06

github-actionsBot added the area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI label Jul 2, 2026

dotnet-policy-serviceBot assigned eduardo-vp Jul 2, 2026

Copilotstarted reviewing on behalf of eduardo-vp July 2, 2026 23:07 View session

CopilotAI reviewed Jul 2, 2026
View reviewed changes

eduardo-vp requested a review from JulieLeeMSFT July 2, 2026 23:13

jkotas approved these changes Jul 2, 2026
View reviewed changes

eduardo-vp merged commit e1979b7 into dotnet:mainJul 3, 2026
88 checks passed

dotnet-maestroBot mentioned this pull request Jul 4, 2026
[main] Source code updates from dotnet/runtime dotnet/dotnet#7544
Merged

dotnet-milestone-botBot added this to the 11.0-preview7 milestone Jul 4, 2026

eduardo-vp mentioned this pull request Jul 6, 2026
Assert failure: Consistency check failed: AV in clr at this callstack #129681
Closed

github-actionsBot locked and limited conversation to collaborators Aug 4, 2026

Update OutOfMemoryException test
306e235

CopilotAI review requested due to automatic review settings July 2, 2026 23:06

github-actionsBot added the area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI label Jul 2, 2026

dotnet-policy-serviceBot assigned eduardo-vp Jul 2, 2026

Copilotstarted reviewing on behalf of eduardo-vp July 2, 2026 23:07 View session

CopilotAI reviewed Jul 2, 2026
View reviewed changes

eduardo-vp requested a review from JulieLeeMSFT July 2, 2026 23:13

jkotas approved these changes Jul 2, 2026
View reviewed changes

eduardo-vp merged commit e1979b7 into dotnet:mainJul 3, 2026
88 checks passed

dotnet-maestroBot mentioned this pull request Jul 4, 2026
[main] Source code updates from dotnet/runtime dotnet/dotnet#7544
Merged

dotnet-milestone-botBot added this to the 11.0-preview7 milestone Jul 4, 2026

eduardo-vp mentioned this pull request Jul 6, 2026
Assert failure: Consistency check failed: AV in clr at this callstack #129681
Closed

github-actionsBot locked and limited conversation to collaborators Aug 4, 2026

Update OutOfMemoryException test
306e235

CopilotAI review requested due to automatic review settings July 2, 2026 23:06

github-actionsBot added the area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI label Jul 2, 2026

dotnet-policy-serviceBot assigned eduardo-vp Jul 2, 2026

Copilotstarted reviewing on behalf of eduardo-vp July 2, 2026 23:07 View session

CopilotAI reviewed Jul 2, 2026
View reviewed changes

eduardo-vp requested a review from JulieLeeMSFT July 2, 2026 23:13

jkotas approved these changes Jul 2, 2026
View reviewed changes

eduardo-vp merged commit e1979b7 into dotnet:mainJul 3, 2026
88 checks passed

dotnet-maestroBot mentioned this pull request Jul 4, 2026
[main] Source code updates from dotnet/runtime dotnet/dotnet#7544
Merged

dotnet-milestone-botBot added this to the 11.0-preview7 milestone Jul 4, 2026

eduardo-vp mentioned this pull request Jul 6, 2026
Assert failure: Consistency check failed: AV in clr at this callstack #129681
Closed

github-actionsBot locked and limited conversation to collaborators Aug 4, 2026

Update OutOfMemoryException test
306e235

CopilotAI review requested due to automatic review settings July 2, 2026 23:06

github-actionsBot added the area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI label Jul 2, 2026

dotnet-policy-serviceBot assigned eduardo-vp Jul 2, 2026

Copilotstarted reviewing on behalf of eduardo-vp July 2, 2026 23:07 View session

CopilotAI reviewed Jul 2, 2026
View reviewed changes

eduardo-vp requested a review from JulieLeeMSFT July 2, 2026 23:13

jkotas approved these changes Jul 2, 2026
View reviewed changes

eduardo-vp merged commit e1979b7 into dotnet:mainJul 3, 2026
88 checks passed

dotnet-maestroBot mentioned this pull request Jul 4, 2026
[main] Source code updates from dotnet/runtime dotnet/dotnet#7544
Merged

dotnet-milestone-botBot added this to the 11.0-preview7 milestone Jul 4, 2026

eduardo-vp mentioned this pull request Jul 6, 2026
Assert failure: Consistency check failed: AV in clr at this callstack #129681
Closed

github-actionsBot locked and limited conversation to collaborators Aug 4, 2026

Update OutOfMemoryException test
306e235

CopilotAI review requested due to automatic review settings July 2, 2026 23:06

github-actionsBot added the area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI label Jul 2, 2026

dotnet-policy-serviceBot assigned eduardo-vp Jul 2, 2026

Copilotstarted reviewing on behalf of eduardo-vp July 2, 2026 23:07 View session

CopilotAI reviewed Jul 2, 2026
View reviewed changes

eduardo-vp requested a review from JulieLeeMSFT July 2, 2026 23:13

jkotas approved these changes Jul 2, 2026
View reviewed changes

eduardo-vp merged commit e1979b7 into dotnet:mainJul 3, 2026
88 checks passed

dotnet-maestroBot mentioned this pull request Jul 4, 2026
[main] Source code updates from dotnet/runtime dotnet/dotnet#7544
Merged

dotnet-milestone-botBot added this to the 11.0-preview7 milestone Jul 4, 2026

eduardo-vp mentioned this pull request Jul 6, 2026
Assert failure: Consistency check failed: AV in clr at this callstack #129681
Closed

github-actionsBot locked and limited conversation to collaborators Aug 4, 2026

	if(args.Length>0&&args[0]==AllocateSmallArg)
	{
	// Pre-allocate a flat array for storage.
	object[]storage=newobject[8192];
	intidx=0;
	// We expect ~2048 iterations in the first loop and ~64 iterations in the second.
	try{while(idx<storage.Length)storage[idx++]=GC.AllocateArray<byte>(16*1024,pinned:true);}catch(OutOfMemoryException){}
	try{while(idx<storage.Length)storage[idx++]=GC.AllocateArray<byte>(256,pinned:true);}catch(OutOfMemoryException){}
	// < 280 bytes free.
	// Use the smallest possible allocation to exhaust the last scraps.
	while(idx<storage.Length)storage[idx++]=GC.AllocateArray<byte>(1,pinned:true);
	returnFail;
	}

Uh oh!

Conversation

eduardo-vp commented Jul 2, 2026

Uh oh!

dotnet-policy-serviceBot commented Jul 2, 2026

Uh oh!

CopilotAI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

eduardo-vp commented Jul 2, 2026

Uh oh!

dotnet-policy-serviceBot commented Jul 2, 2026

Uh oh!

CopilotAI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

eduardo-vp commented Jul 2, 2026

Uh oh!

dotnet-policy-serviceBot commented Jul 2, 2026

Uh oh!

CopilotAI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

eduardo-vp commented Jul 2, 2026

Uh oh!

dotnet-policy-serviceBot commented Jul 2, 2026

Uh oh!

CopilotAI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

eduardo-vp commented Jul 2, 2026

Uh oh!