summaryrefslogtreecommitdiff
path: root/doc/forum/recent_propellor_snapshots_cause_ghc_OOMs
diff options
context:
space:
mode:
authormithrandi@311efa1b2b5c4999c2edae7da06fb825899e8a822016-06-02 20:26:40 +0000
committeradmin2016-06-02 20:26:40 +0000
commit460dc5f68852b0e5e7e55392fc0b48ed186bfcfd (patch)
tree39b4f60a025613e1c8a8bdfedd01a3a10a32ee45 /doc/forum/recent_propellor_snapshots_cause_ghc_OOMs
parent941b0513d6bf4d9c78764e9f3efad3174c5c0846 (diff)
Added a comment
Diffstat (limited to 'doc/forum/recent_propellor_snapshots_cause_ghc_OOMs')
-rw-r--r--doc/forum/recent_propellor_snapshots_cause_ghc_OOMs/comment_7_37a683d847bd7275c6ff7b0ad94af6a6._comment8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/forum/recent_propellor_snapshots_cause_ghc_OOMs/comment_7_37a683d847bd7275c6ff7b0ad94af6a6._comment b/doc/forum/recent_propellor_snapshots_cause_ghc_OOMs/comment_7_37a683d847bd7275c6ff7b0ad94af6a6._comment
new file mode 100644
index 00000000..51b53ba3
--- /dev/null
+++ b/doc/forum/recent_propellor_snapshots_cause_ghc_OOMs/comment_7_37a683d847bd7275c6ff7b0ad94af6a6._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="mithrandi@311efa1b2b5c4999c2edae7da06fb825899e8a82"
+ nickname="mithrandi"
+ subject="comment 7"
+ date="2016-06-02T20:26:40Z"
+ content="""
+I ran into a similar problem, only I had a lot more memory to go through before OOMing (GHC went up to 20 GB). After commenting out part of my configuration, I got a ton of type errors (due to mixing up Property types in a bunch of places, as well as having a missing `props`). Once I fixed the type errors and then uncommenting everything, complication proceeded as normal. So I think there is some pathological case here that causes some blowup in compilation when the types don't line up properly, possible due to some exponential complexity somewhere.
+"""]]