Han-Wen Nienhuys schreef op vr 10-12-2021 om 15:59 [+0100]:
> On the one hand, the docs for smobs state "must assume .. all SCM
> values that it references have already been freed and are thus
> invalid", which suggests that smob freeing happens in random order,
> which is consistent with what we
Han-Wen Nienhuys schreef op vr 10-12-2021 om 15:59 [+0100]:
> We can change our mark routines to avoid the crash, but it's unclear
> to us if this behavior is intended or not, and we worry that this
> will
> come back to bite us in the future.
> [...]
> [... things about Java-style finalisation
Hi,
Han-Wen Nienhuys schreef op vr 10-12-2021 om 15:59 [+0100]:
> which is consistent with what we see. On the other hand, Guile sets
> up
> BDWGC with GC_java_finalization=1, which should keep GC dependencies
At least in Guile 3, that's done in scm_init_guardians.
While that's always called in
Hi Guile devs,
We are debugging a GC issue in LilyPond when used with Guile 2.2, and
could use some help.
The issue and associated Merge Request are here:
https://gitlab.com/lilypond/lilypond/-/issues/6218
https://gitlab.com/lilypond/lilypond/-/merge_requests/1035
We are using smobs with
