Re: BDWGC fix in 2.24?

[Jonas Hahnfeld]

On Sat, 2022-11-19 at 22:29 +0100, Jonas Hahnfeld via Discussions on
LilyPond development wrote:
> > In https://github.com/ivmai/bdwgc/issues/454#issuecomment-1313127991
> > the BDWGC maintainer said the release of his fix would
> > probably happen in January, which is later than what we
> > hope for our 2.24 release.
> > 
> > What should we do? Do we accept releasing 2.24 from
> > the release-8_2 branch in BDWGC even though it is not
> > released? Do we keep the current workaround, which still
> > gives some crashes? Do we replace our workaround
> > with Ivan Maidanski's patch, which seems to apply cleanly
> > on the v.8.2.2 tag?
> 
> I personally think this should not block the release, simply because
> big scores have been a pain point on Windows before due to 32-bit
> limitations [1]. It would of course be nice to fix it (and _maybe_ we
> can patch in only the minimal parts of the patch)

I played a bit this week, and at least the crash for the score in
https://lists.gnu.org/archive/html/lilypond-user/2022-11/msg00272.html
(which is finally a crash that I can reproduce) seems to be solved by
the current tip of the release-8_2 branch. A minimal backport of that
commit on its own also seems to work. However, my original plan was to
keep the current workaround in place *and* backport a minimal version
of the fix. For some inexplicable reasons, this avoids the crash but
then just hangs after printing the warning (that I did not patch). This
doesn't make me feel comfortable doing any last minute change in that
area, potentially breaking things even worse, and I will not do it for
this weekend.

Jonas

signature.asc
Description: This is a digitally signed message part