I don't think treating this separately to bug 1506358 will be helpful.
Firstly, there is proof in comment #40 that the original reporter hit bug 1506358 at 13:31:08 on 10 January. Assuming Uranicus is 1 hour ahead of UTC...
Secondly, if you look in bug 1506358 you'll find I mentioned that when it occurs (client crashes) the server is unaffected and keeps running. In the case of this bug where unity8 is the client, unity-system-compositor is the server. So if unity-system-compositor has issues at all it's likely unrelated to bug 1506358. And the bug most provably related to this one is bug 1506358.
I don't think treating this separately to bug 1506358 will be helpful.
Firstly, there is proof in comment #40 that the original reporter hit bug 1506358 at 13:31:08 on 10 January. Assuming Uranicus is 1 hour ahead of UTC...
Secondly, if you look in bug 1506358 you'll find I mentioned that when it occurs (client crashes) the server is unaffected and keeps running. In the case of this bug where unity8 is the client, unity-system- compositor is the server. So if unity-system- compositor has issues at all it's likely unrelated to bug 1506358. And the bug most provably related to this one is bug 1506358.