Comment #0 by destructionator — 2022-02-08T15:47:31Z
I don't have a minimized example, this came up in the middle of a large work application, but examining the source code and the stack trace reveals the issue.
The destructor is @nogc hoping to avoid these, but this slipped through. I'm not sure if it should actually fail the nogc check (though it does fail a nothrow check which is interesting but not necessarily a bug per se), but regardless we should do something.
synchronized(this) calls ensureMontior which calls GC.setAttr which throws the invalid memory operation error.
Comment #1 by robert.schadek — 2024-12-13T19:20:50Z