This is a follow-up from bug 724878: the permission manager is now doing all actions on DB asynchronously except initialization. Making the initialization async could help a lot because that's the heaviest IO the permission manager is doing (basically, reading the DB to have an internal representation in memory). Unfortunately, the permission manager being initialized lazily, it's very likely that after the init, we will try to read something from the loaded permissions, making the permission check waiting on the DB being fully read. Based on that, I'm not sure how helpful it would be to have the permission manager init doing async DB access...