Support tried to tell me that this problem doesn't exist in the stable firmware (I guess you're all lying?), pointed them at some threads here to try and convince them that it does exist. This is harder to do than it should be.

show them screenshot from firmware version & the error message

babis3g wrote: show them screenshot from firmware version & the error message

I've discussed it at length with the support rep and described the issue in quite some detail. They're convinced that it's limited to my beta version (Which I've been running since March 31st 2015, I reported this session issue 2 weeks after starting to use the beta) and that the stable version does not have this issue.

I really hope these threads convince them otherwise.