This looks similar to a bug we found in our internal tests and for which we have implemented a patch (not released yet). But to make sure, can you tell us who the owner of the session is? You can see this info in the session list once you’ve authenticated e.g User ‘nomachine’.
