Thread overview
[Issue 15595] access violation on GC-allocated memory during GC collection
Oct 18, 2016
anonymous4
Oct 18, 2016
anonymous4
Dec 17, 2022
Iain Buclaw
October 18, 2016
https://issues.dlang.org/show_bug.cgi?id=15595

anonymous4 <dfj1esp02@sneakemail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Hardware|x86_64                      |All
           See Also|                            |https://issues.dlang.org/sh
                   |                            |ow_bug.cgi?id=4621
            Summary|access violation in         |access violation on
                   |_d_interface_cast during GC |GC-allocated memory during
                   |collection                  |GC collection
                 OS|Windows                     |All

--- Comment #1 from anonymous4 <dfj1esp02@sneakemail.com> ---
Slightly repurposing the bug. Current implementation of GC doesn't support referencing GC-allocated memory during collection because it's freed out of order.

--
October 18, 2016
https://issues.dlang.org/show_bug.cgi?id=15595

anonymous4 <dfj1esp02@sneakemail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gamezelda2@gmail.com

--- Comment #2 from anonymous4 <dfj1esp02@sneakemail.com> ---
*** Issue 6223 has been marked as a duplicate of this issue. ***

--
December 17, 2022
https://issues.dlang.org/show_bug.cgi?id=15595

Iain Buclaw <ibuclaw@gdcproject.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P1                          |P4

--
December 07
https://issues.dlang.org/show_bug.cgi?id=15595

--- Comment #3 from dlangBugzillaToGithub <robert.schadek@posteo.de> ---
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

--