Hi, Martin.

There's a very small subset of people that occasionally get this problem. We're working to try and isolate it a bit more - and we're making some progress on that. It seems to be a third party component we're using - and we're waiting for an update to fix it (hopefully) - probably sometime in November. Once we've verified that this fixes things, we'll probably do an update relatively quickly.

- Pete