summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2016-02-26 13:54:58 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2016-02-26 13:54:58 -0400
commitab71eec1033aa7af610c1b4206d2dbf64e5c1e68 (patch)
tree487efb7fb02bc55610c94d271de5d55c29c6948e
parentafc6b48604da577b9c638c73ee2ccaec3e96cb84 (diff)
update
-rw-r--r--doc/bugs/checksum_loads_whole_file_into_memory.mdwn5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/bugs/checksum_loads_whole_file_into_memory.mdwn b/doc/bugs/checksum_loads_whole_file_into_memory.mdwn
index c00d3a96b..9b121843a 100644
--- a/doc/bugs/checksum_loads_whole_file_into_memory.mdwn
+++ b/doc/bugs/checksum_loads_whole_file_into_memory.mdwn
@@ -11,3 +11,8 @@ Commit 7482853ddddc21f2696dcfbc82d737f03032134a may be relevant,
but I don't understand how yet. A small test program using the same
code doesn't exhibit the problem, even when built in the identical build
environment as the 6.20160217-g95bbdb8 that has the problem.
+
+> Update: Reverted 7482853ddddc21f2696dcfbc82d737f03032134a and indeed the
+> problem got fixed. But, reverting that commit breaks the test suite on
+> windows and has a FD leak, so is not desirable. This needs more
+> investigation. --[[Joey]]