On Monday, 1 March 2021 at 09:03:32 UTC, rikki cattermole wrote:
So it is debatable if it is a good idea to get rid of them once
done (even if delayed).
Makes sense, Thanks a lot for the quick help!
On 01/03/2021 8:02 PM, Keivan Shah wrote:
If possible, Can you also help me understand that why are the threads
not despawned once the GC is done collecting in this example?
There was a PR about this ages ago.
But one thing to consider is that keeping threads around not doing
anything
On Monday, 1 March 2021 at 06:50:42 UTC, rikki cattermole wrote:
Do you still get them when you call your app like this?
./app --DRT-gcopt=parallel:0
Wow, Not getting with "--DRT-gcopt=parallel:0", Thanks a lot,
didn't know GC had a parallel option that can be
Do you still get them when you call your app like this?
./app --DRT-gcopt=parallel:0
I had recently updated my dmd version to latest, i.e from 2.076.1
(I know, sorry) to 2.095.0 and suddenly my code has started
spawning extra threads which were not there before with no
obvious reasons, after trying to simplify and identify the cause
as much as possible, I have come up with
