Reply to thread

It is possible. The OOM errors were caused by the loading of XFMG session activity details. We did change that code in XFMG 1.0.2. Unfortunately at the time we had a lack of information and you reported the error had gone away hence we couldn't see that the issue was related. As I said to you before, if the problem continued you needed to let us know so we could look into it further.