From 65a7716a93960ea1418927bd9d4df22ad8fb9e21 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 2 Jun 2016 17:20:51 -0400 Subject: include description in example --- .../comment_8_b20c69390343bf3b2a7f7b6776f43389._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/recent_propellor_snapshots_cause_ghc_OOMs/comment_8_b20c69390343bf3b2a7f7b6776f43389._comment (limited to 'doc/forum/recent_propellor_snapshots_cause_ghc_OOMs') diff --git a/doc/forum/recent_propellor_snapshots_cause_ghc_OOMs/comment_8_b20c69390343bf3b2a7f7b6776f43389._comment b/doc/forum/recent_propellor_snapshots_cause_ghc_OOMs/comment_8_b20c69390343bf3b2a7f7b6776f43389._comment new file mode 100644 index 00000000..df8c6222 --- /dev/null +++ b/doc/forum/recent_propellor_snapshots_cause_ghc_OOMs/comment_8_b20c69390343bf3b2a7f7b6776f43389._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 8""" + date="2016-06-02T21:04:33Z" + content=""" +@mithrandi there are ways to make ghc type error messages arbitrarily long, +and IIRC that causes the memory to blow up. + +I'm mostly interested in memory blowups when building a valid +configuration, since those cause problems to the hosts propellor is +deployed to, rather than just to the system where it's developed. +"""]] -- cgit v1.2.3