Skip to content
This repository has been archived by the owner on Oct 12, 2022. It is now read-only.

Forbid interacting with the GC while a collection is in progress, to avoid memory corruption (issue 5653) #16

Merged
merged 1 commit into from
May 28, 2011

Conversation

CyberShadow
Copy link
Member

This will also forbid interacting with the GC after a finalizer throws an exception.

…avoid memory corruption

This will also forbid interacting with the GC after a finalizer throws an exception.
andralex added a commit that referenced this pull request May 28, 2011
Forbid interacting with the GC while a collection is in progress, to avoid memory corruption (issue 5653)
@andralex andralex merged commit 0a18e49 into dlang:master May 28, 2011
CyberShadow added a commit to CyberShadow/druntime that referenced this pull request Sep 22, 2011
In pull request dlang#16, I closed off a dangerous memory-corruption problem
by making the GC throw an exception in circumstances which otherwise
would result in undefined behavior (and ultimately memory corruption).
Since I was lazy and afraid to make larger changes, I reused the existing
OutOfMemoryError class - however, since then, I've heard several times
about D users being confused about OOM conditions when their app is
clearly not lacking memory. This patch rectifies the problem, and
introduces and documents a new exception class dedicated for invalid
memory operations.
redstar added a commit to redstar/druntime that referenced this pull request Sep 1, 2015
MinGW-x64: fix unresolved symbol problems during linking
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants