unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mike Gran <spk121@yahoo.com>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: Jonas Hahnfeld <hahnjo@hahnjo.de>,
	Maxime Devos <maximedevos@telenet.be>,
	guile-devel@gnu.org
Subject: Re: GC + Java finalization
Date: Tue, 22 Feb 2022 07:12:59 -0800	[thread overview]
Message-ID: <YhT9e7YhJi+9jiAh@spikycactus.com> (raw)
In-Reply-To: <87mtij2oo0.fsf@web.de>

On Tue, Feb 22, 2022 at 11:14:16AM +0100, Dr. Arne Babenhauserheide wrote:
> 
> Jonas Hahnfeld via "Developers list for Guile, the GNU extensibility library" <guile-devel@gnu.org> writes:
> 
> > [[PGP Signed Part:Good signature from 91C9C33D2C61ACDB Jonas Hahnfeld <jonas.hahnfeld@gmail.com> (trust undefined) created at 2021-11-19T13:18:31+0100 using RSA]]
> > Am Sonntag, dem 10.10.2021 um 18:22 +0200 schrieb Jonas Hahnfeld via
> > Developers list for Guile, the GNU extensibility library:
> >> Am Donnerstag, dem 15.07.2021 um 20:44 +0200 schrieb Jonas Hahnfeld via
> >> Developers list for Guile, the GNU extensibility library:
> >> > Am Samstag, dem 03.07.2021 um 14:05 +0200 schrieb Jonas Hahnfeld via
> >> > Developers list for Guile, the GNU extensibility library:
> >> > > Hi Guile devs,
> >> > > 
> >> > > I'm hacking on GNU LilyPond and recently wondered if Guile could run
> >> > > without Java finalization that prevents collection of chains of
> >> > > unreachable objects. I found that the functionality is only needed once
> >> > > the first guardian is created, so it's possible to delay enabling the
> >> > > mode until then. This required some fixes to free functions that
> >> > > assumed dependent objects to be freed only later (see first two
> >> > > patches).
> >> > > The third patch delays ensuring Java finalization to scm_make_guardian,
> >> > > but doesn't disable it explicitly (it's on by default in bdwgc). This
> >> > > could now be done right after GC_INIT(), but it's not clear (at least
> >> > > to me) whether client applications actually rely it, so I think it's
> >> > > better if that's not done in Guile itself.
> >> > > 
> >> > > Please consider applying, the fixes potentially also to stable-2.2.
> >> > 
> >> > I didn't receive other comments than those by Maxime, so here is an
> >> > updated version of the first patch.
> >> 
> >> Ping, is there anybody looking at patches sent to the mailing list?
> >
> > Last ping before I give up...
> 
> Did someone now look into the patches?

Arne,

It is likely that a few people saw the patches, but, no one person
with commit access felt like he or she should be the person to fix it
or champion it.

The maintainers have always seemed amenable to allowing the committers
to fix things without a lot of process, but, Guile as a project
is not structured to encourage committers to look through the patch
and bug backlog.

I've seen some e-mail traffic about how to fix it, but, I don't think
a consensus had been reached.

(I say this as a bystander and former committer; I don't speak for
the project.)

-Mike
> 
> Best wishes,
> Arne
> -- 
> Unpolitisch sein
> hei�t politisch sein,
> ohne es zu merken.
> draketo.de





  reply	other threads:[~2022-02-22 15:12 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-03 12:05 GC + Java finalization Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2021-07-03 17:14 ` Maxime Devos
2021-07-03 17:26   ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2021-07-03 18:49     ` Maxime Devos
2021-07-03 18:54     ` Maxime Devos
2021-07-15 18:44 ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2021-10-10 16:22   ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2021-11-19 12:18     ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2022-02-22 10:14       ` Dr. Arne Babenhauserheide
2022-02-22 15:12         ` Mike Gran [this message]
2021-11-19 13:13   ` Maxime Devos
2021-11-19 13:32     ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2021-11-19 13:35       ` Maxime Devos
2021-11-19 13:40         ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2021-11-19 13:44           ` Maxime Devos
2021-11-19 13:53             ` Maxime Devos
2021-11-19 13:53             ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2021-11-19 14:01               ` Maxime Devos
2021-11-19 13:48       ` Maxime Devos
2021-11-19 13:55         ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2021-11-19 14:14           ` Maxime Devos
2021-11-19 14:52             ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2021-11-19 18:48               ` Maxime Devos
2021-11-19 19:01                 ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2021-11-19 13:15   ` Maxime Devos
2021-11-19 13:35     ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2021-11-19 14:21       ` Maxime Devos
2021-11-19 15:32         ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2021-11-19 13:17   ` Maxime Devos
2021-11-19 13:38     ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2021-11-20  9:19   ` Maxime Devos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YhT9e7YhJi+9jiAh@spikycactus.com \
    --to=spk121@yahoo.com \
    --cc=arne_bab@web.de \
    --cc=guile-devel@gnu.org \
    --cc=hahnjo@hahnjo.de \
    --cc=maximedevos@telenet.be \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).