From ba7598dbabcac92de747bf10d2c26dd6a6572e63 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 12 May 2021 13:39:15 -0400 Subject: [PATCH] comment --- ..._2a991ec73fa2e065d01568e2c3e341fd._comment | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 doc/bugs/internal_error__58___evacuate__58___strange_closure_type/comment_1_2a991ec73fa2e065d01568e2c3e341fd._comment diff --git a/doc/bugs/internal_error__58___evacuate__58___strange_closure_type/comment_1_2a991ec73fa2e065d01568e2c3e341fd._comment b/doc/bugs/internal_error__58___evacuate__58___strange_closure_type/comment_1_2a991ec73fa2e065d01568e2c3e341fd._comment new file mode 100644 index 0000000000..eead56a68e --- /dev/null +++ b/doc/bugs/internal_error__58___evacuate__58___strange_closure_type/comment_1_2a991ec73fa2e065d01568e2c3e341fd._comment @@ -0,0 +1,24 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2021-05-12T17:09:06Z" + content=""" +I'm seeing this too, although sometimes it seems to crash out before that +gets written to the log. And sometimes it manages to get running and seems +to run ok. + +It does not happen with --foreground AFAICS. + +Reproduced it with that most recent standalone release, and also with a +local dev build, also with ghc 8.8.4. + +This would usually be a ghc or library bug, as there's no code in git-annex +low-level enough to cause this kind of memory corruption or whatever it is. + +But, the assistant does one really funky thing for a haskell program, and that +is forking to the background. It seems just possible that doing that has +started confusing the garbage collector in some way. + +forkProcess is really problimatic with its handling of threads etc, +and this may be the signal that git-annex needs to stop using it. +"""]] -- 2.30.2