summaryrefslogtreecommitdiff
path: root/doc/forum/recent_propellor_snapshots_cause_ghc_OOMs/comment_8_b20c69390343bf3b2a7f7b6776f43389._comment
blob: df8c6222d98143ccfe31576d59b357f445db4f40 (plain)
1
2
3
4
5
6
7
8
9
10
11
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.
"""]]