F*cked by memory corruption after assiging value to associative array
frame
frame86 at live.com
Wed Jan 27 17:10:58 UTC 2021
On Tuesday, 26 January 2021 at 14:31:58 UTC, frame wrote:
but why does not see DLL 1 then that sub objects of
> B are still alive?
I may fool myself but could it be caused by an already gone slice
data? It very looks like that only a specific string property is
corrupted which got the same slice data as an input parameter.
I thought that the slice data should stay referenced in the
persistent object anyway but the GC seems not so smart to detect
this.
The error can be prevented with .dup so far.
More information about the Digitalmars-d-learn
mailing list