From 021df438c4c08039ab5fd957d14f1dcb7aefd863 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Mon, 10 Mar 2014 18:12:29 +0000 Subject: [PATCH] Added a comment --- .../comment_8_b9aab0aba4dab30260371b4762e0e51d._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/enormous_fsck_output_OOM/comment_8_b9aab0aba4dab30260371b4762e0e51d._comment diff --git a/doc/bugs/enormous_fsck_output_OOM/comment_8_b9aab0aba4dab30260371b4762e0e51d._comment b/doc/bugs/enormous_fsck_output_OOM/comment_8_b9aab0aba4dab30260371b4762e0e51d._comment new file mode 100644 index 0000000000..fa437311fc --- /dev/null +++ b/doc/bugs/enormous_fsck_output_OOM/comment_8_b9aab0aba4dab30260371b4762e0e51d._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="108.236.230.124" + subject="comment 8" + date="2014-03-10T18:12:29Z" + content=""" +In a quick test with a 32 mb dummy fsck output, git-repair ballooned up to 1.7 gb. Clearly something not happy there, although in my case this did not cause it to crash. +"""]]