Comment 4 for bug 1379296

In theory, this landed and is in rtm krillin image 112... but on 112 I've had unity8 get OOM-killed twice in the past couple hours.

The first time, posclientd basically freaked out (sorry, vague) and pegged the CPU, and soon afterward unity8 got OOM killed. For that matter, apport failed too, due to insufficient memory.

The second time, media-hub went into a similar resource-hogging loop and unity8 got killed... and apport was again unable to get a useful result due to memory.

So... not actually fixed?