Bug#900173: git-annex: internal error: evacuate: strange closure type 4325404

[Anthony DeRobertis]

On 05/27/2018 10:55 AM, Sean Whitton wrote:
> This isn't enough information about how to reproduce this bug for me to
> be comfortable forwarding it upstream, but I've CCed upstream just in
> case he recognises the error message.

I hear you! But that's the entire log file ...

I also managed to produce a similar message, by using the "restart 
daemon" option in the webapp:

[2018-05-27 09:50:55.085069462] NetWatcherFallback: Syncing with public, zia, einstein
Everything up-to-date
Everything up-to-date
[2018-05-27 10:50:55.968806564] NetWatcherFallback: Syncing with public, zia, einstein
Everything up-to-date
Everything up-to-date
tail: '/home/anthony/Westerley-Board/.git/annex/daemon.log' has been replaced;  following new file
[2018-05-27 11:01:09.077123603] main: starting assistant version 6.20180509
git-annex: internal error: evacuate: strange closure type 1061
     (GHC version 8.2.2 for x86_64_unknown_linux)
     Please report this as a GHC bug:  http://www.haskell.org/ghc/reportabug

At this point, git annex assistant --stop doesn't work and I have to 
kill the git-annex process. After that, git annex assistant produces 
another very similar message:

tail: '/home/anthony/Westerley-Board/.git/annex/daemon.log' has appeared;  following new file
[2018-05-27 11:04:00.911450237] main: starting assistant version 6.20180509
git-annex: internal error: evacuate: strange closure type 4325407
     (GHC version 8.2.2 for x86_64_unknown_linux)
     Please report this as a GHC bug:  http://www.haskell.org/ghc/reportabug


Trying again a few times produces similar messages, just with different 
numbers. This all works perfectly fine on a new test repository ... and 
it seems removing webapp.html wasn't actually what fixed it, I just need 
to wait long enough. Or something. It went away randomly one time I 
tried it. And now restarting the webapp is working.

Confusing. Just to be sure, going to reboot this machine into memtest 
(which was done before I first started using it, but you never know...)