GC issue? List.pool overwritten by allocated object
Denis Feklushkin
feklushkin.denis at gmail.com
Sat May 17 20:31:22 UTC 2025
On Friday, 16 May 2025 at 22:55:33 UTC, Denis Feklushkin wrote:
> On Friday, 16 May 2025 at 20:26:44 UTC, Denis Feklushkin wrote:
>> As a result, a new `List` is formed without `malloc()` call.
>> This list contains a pointer to the some pool. Apparently,
>> this memory is taken from a previously used pool. But at the
>> same time, the memory that this pointer points to looks as has
>> never been touched by any D code.
>
> ...and into this memory writes Vulkan library, as into its own
> allocated memory
I'm really tired of researching this issue. Maybe someone else
also interested?
Just made a branch with latest dirty debug changes:
```
git clone --branch=manual_reduce
git at github.com:denizzzka/pukan.git
```
commit: 34dff13e76bb6ffbe9053eb8cad8f8f33a850b94
More information about the Digitalmars-d
mailing list