[Issue 3523] [GC] Fiber is not garbage collected properly

[d-bugmail--- via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=3523

--- Comment #16 from Witold Baryluk  ---
Steven, yes this is still an issue with current compiler and runtime.

The issue is that yes, it probably is possible to exclude references from one
fiber to itself, but there might be weird cases where there are complex chains
of fibers pointing to each other, and whole chains isn't accessible from
anywhere else, or even from each fiber directly, but it is hard to tell if it
is a garbage or not. But if all elements in the chain are in TERM state, or
only leaves in the graph are in TERM state, that should be doable. But i have
no idea if GC can compute such condition efficiently.

--

[Issue 3523] [GC] Fiber is not garbage collected properly

[d-bugmail--- via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=3523

Steven Schveighoffer  changed:

   What|Removed |Added

 CC||schvei...@yahoo.com

--- Comment #15 from Steven Schveighoffer  ---
This is pretty old, but I wonder if it's still broken?

>From this recent thread, it may already be fixed, as peppering in GC
collections seems to solve the problem:

https://forum.dlang.org/post/vfqvmyossdcqadgas...@forum.dlang.org

I was coming to file a bug on this, but this seems (at least) to be close to
explaining what is happening.

Note that we have a separate issue with Fibers and GC. The GC only associates a
small block with the Fiber -- the Fiber object itself, whereas the stack is
huge comparatively. In 32-bit windows, a fiber stack is default 32k. This means
that 10,000 Fibers probably takes up 1.2MB in the GC (assuming 128 bytes per
fiber), but the stack space is 320MB. There is a lack of correlation here
between memory pressure and when the memory should be cleaned up.

Would it be possible to deallocate the stack when the Fiber terminates vs. when
it's GC'd? That would at least help with Fibers that are completed and just
left for garbage.

--

[Issue 3523] [GC] Fiber is not garbage collected properly

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=3523

Andrei Alexandrescu  changed:

   What|Removed |Added

   Keywords||bootcamp
 CC||and...@erdani.com

--

[Issue 3523] [GC] Fiber is not garbage collected properly

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=3523

Andrei Alexandrescu and...@erdani.com changed:

   What|Removed |Added

Version|2.032   |D2

--

[Issue 3523] [GC] Fiber is not garbage collected properly

[d-bugmail]

https://d.puremagic.com/issues/show_bug.cgi?id=3523


Martin Nowak c...@dawg.eu changed:

   What|Removed |Added

   Priority|P2  |P3


--- Comment #14 from Martin Nowak c...@dawg.eu 2013-12-13 15:53:42 PST ---
Seems like this was responsible for a performance regression in vibe.d.
https://github.com/rejectedsoftware/vibe.d/commit/1488d5c7426ff7acc1d0bceef5667066354c1191

-- 
Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email
--- You are receiving this mail because: ---