Comment 336 for bug 195698

We're not going to block on this issue, but please do not take that as a statement of disinterest in terms of fixing it.

At 200+ comments, it's nigh impossible for me to get a good sense of what's causing this bug. It's related to session restore, I see, and to having a master password, but the solution being proposed seems to be deep within the networking voodoo. Can we not just do something to the session restore code that looks like:

 - check to see if the profile has a master password
 - if it does, ask the user for their password before restoring the session

cc'ing Johnath, as making the Master Password stuff better is very much going to be his bailiwick.