Ok the OOM killer is in play here so we have clearly run out of memory:
Nov 4 13:08:50 utah-29294-vivid-amd64 kernel: [ 245.136816] gtk-update-icon invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=-1000
1) does UTAH configure the system with any swap, and 2) how much overhead does UTAH contribute in the running image monitoring it.
Ok the OOM killer is in play here so we have clearly run out of memory:
Nov 4 13:08:50 utah-29294- vivid-amd64 kernel: [ 245.136816] gtk-update-icon invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=-1000
1) does UTAH configure the system with any swap, and
2) how much overhead does UTAH contribute in the running image monitoring it.