diff --git a/doc/bugs/v7_unlock_big_file__58___out_of_memory/comment_1_b5adba30830051c4ef93e1ea486757f7._comment b/doc/bugs/v7_unlock_big_file__58___out_of_memory/comment_1_b5adba30830051c4ef93e1ea486757f7._comment
new file mode 100644
index 0000000000..564b94a847
--- /dev/null
+++ b/doc/bugs/v7_unlock_big_file__58___out_of_memory/comment_1_b5adba30830051c4ef93e1ea486757f7._comment
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2019-01-22T21:45:10Z"
+ content="""
+Yeah, so git status is OOMing, not git-annex. (And git commit OOMs too BTW.)
+
+I think git is just naively trying to malloc enough memory for the
+entire file even though it's configured to use the smudge/clean filter
+and the actual data it needs to deal with is small.
+
+I've mentioned this on the git mailing list, in message-id
+`<20190122220714.GA6176@kitenet.net>`.
+"""]]