summaryrefslogtreecommitdiff
path: root/doc/forum/recent_propellor_snapshots_cause_ghc_OOMs
diff options
context:
space:
mode:
Diffstat (limited to 'doc/forum/recent_propellor_snapshots_cause_ghc_OOMs')
-rw-r--r--doc/forum/recent_propellor_snapshots_cause_ghc_OOMs/comment_8_b20c69390343bf3b2a7f7b6776f43389._comment12
1 files changed, 12 insertions, 0 deletions
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.
+"""]]