mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

followup

Browse source
This commit is contained in:
Joey Hess 2019-11-13 15:56:59 -04:00
parent 0096db7b42
commit 98954aaf2c
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 35 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

24
doc/bugs/concurrent_git-annex-copy_to_s3_special_remote_fails/comment_3_f244825dcd89cd6bc74deec7ac4bdd99._comment Normal file
View file

@ -0,0 +1,24 @@
[[!comment format=mdwn
username="joey"
subject="""comment 3"""
date="2019-11-13T19:29:34Z"
content="""
--debug might provide some clue in its http dump.
The ParseError comes from attoparsec. Seems likely that aeson/aws is what's
using it there, and that it is failing to parse something from S3.
Of course, the malloc error suggests a low-level memory problem, probably
from C code. I don't think git-annex contains anything like that, so it
must be from a dependency.
The S3 signature being wrong again points to the aws library, or something
lower level. And then the following double free is another low-level memory
problem.
So there's a pattern, and it seems to extend across linux and OSX.
Kind of wondering if something in the library stack is somehow failing to
be concurrency safe. If two http requests end up using the same memory,
it would kind of explain all of this.
"""]]

11
doc/bugs/parallel_copy_fails/comment_2_6a0e3514a111d48662bb50ca6a15b01f._comment Normal file
View file

@ -0,0 +1,11 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2019-11-13T19:37:16Z"
content="""
The signal 11 is very significant. It points to a problem in a lower-level
library (or ghc runtime), or perhaps a bad memory problem. git-annex does
not itself contain any code that can segfault, afaik.
Almost certianly the same as the other bug.
"""]]