(In reply to Pablo from comment #7) > i am able to reproduce it everywhere, latest nightly, beta and release. > > You just have to: > Open firefox and create a new profile, and launch it. > then close firefox and launch again with the same profile, > then close firefox and launch again with the same profile > then close firefox launch again with the same profile. > > in some cases it took 4 launches and in some cases 3 launches for the restore screen to appear. but i can get it 100% of the times with those steps I tried this with "AVAST One" installed on a Win7 VM, and I cannot reproduce. Are you using the profile manager with every launch, or no? How are you launching Firefox? Can you check the contents (list of files) of the profile directory's `sessionstore-backups` folder before each launch, and tell me what the contents look like on each launch, especially the one where it breaks? If you change `sessionstore.max_resumed_crashes` in about:config to, say, 5, does the issue become harder to reproduce?
Bug 1749996 Comment 29 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Pablo from comment #7) > i am able to reproduce it everywhere, latest nightly, beta and release. > > You just have to: > Open firefox and create a new profile, and launch it. > then close firefox and launch again with the same profile, > then close firefox and launch again with the same profile > then close firefox launch again with the same profile. > > in some cases it took 4 launches and in some cases 3 launches for the restore screen to appear. but i can get it 100% of the times with those steps I tried this with "AVAST One" installed on a Win7 VM (per comment 26), and I cannot reproduce. Are you using the profile manager with every launch, or no? How are you launching Firefox? Can you check the contents (list of files) of the profile directory's `sessionstore-backups` folder before each launch, and tell me what the contents look like on each launch, especially the one where it breaks? If you change `sessionstore.max_resumed_crashes` in about:config to, say, 5, does the issue become harder to reproduce?