← Back to index | Original Bugzilla link

Bug 15595 – access violation on GC-allocated memory during GC collection

Status: NEW
Severity: enhancement
Priority: P4
Component: druntime
Product: D
Version: D2
Platform: All
OS: All
Creation time: 2016-01-23T05:32:42Z
Last change time: 2024-12-07T13:36:16Z
Assigned to: No Owner
Creator: Etienne
See also: https://issues.dlang.org/show_bug.cgi?id=4621

Comments

Comment #0 by etienne — 2016-01-23T05:32:42Z

When using Unique!Object, if Object is collected by the GC during the same collection cycle that calls the destructor of an object containing Unique!, the destroy() function will produce an access violation during casting, because the vtable pointer is no longer valid.

Comment #1 by dfj1esp02 — 2016-10-18T08:08:10Z

Slightly repurposing the bug. Current implementation of GC doesn't support referencing GC-allocated memory during collection because it's freed out of order.

Comment #2 by dfj1esp02 — 2016-10-18T08:09:10Z

*** Issue 6223 has been marked as a duplicate of this issue. ***

Comment #3 by robert.schadek — 2024-12-07T13:36:16Z

THIS ISSUE HAS BEEN MOVED TO GITHUB https://github.com/dlang/dmd/issues/17323 DO NOT COMMENT HERE ANYMORE, NOBODY WILL SEE IT, THIS ISSUE HAS BEEN MOVED TO GITHUB