Bug 1983990 Comment 3 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 Olivier Mehani [:shtrom] from comment #2)
> I checked right now, and can't find the `sessionstore.jsonlz4` file.
> 
> ```
> $ find -name sessionstore\*
> ./sessionstore-logs
> ./sessionstore-backups
> ./chrome_debugger_profile/sessionstore-logs
> $ ls sessionstore-backups
> previous.jsonlz4  recovery.jsonlz4                upgrade.jsonlz4-20250819213618
> recovery.baklz4   upgrade.jsonlz4-20250817090944  upgrade.jsonlz4-20250820095721
> ```
> 
> Where should it be?
> 
> I have found the backup, though, so that's good.
> 
> Also, is this a relevant test to do now, or should I wait until there is a session restore issue?

Sorry for the delay. Interesting that you can't find that file... I think you could try it now, keeping in mind if you have created new groups or pinned tabs it'll override those. So its up to you if you want to try it now or wait until this happens again. Although I'm hoping we can tackle an intervention to avoid the need for this in the future - see 1906808.
(In reply to Olivier Mehani [:shtrom] from comment #2)
> I checked right now, and can't find the `sessionstore.jsonlz4` file.
> 
> ```
> $ find -name sessionstore\*
> ./sessionstore-logs
> ./sessionstore-backups
> ./chrome_debugger_profile/sessionstore-logs
> $ ls sessionstore-backups
> previous.jsonlz4  recovery.jsonlz4                upgrade.jsonlz4-20250819213618
> recovery.baklz4   upgrade.jsonlz4-20250817090944  upgrade.jsonlz4-20250820095721
> ```
> 
> Where should it be?
> 
> I have found the backup, though, so that's good.
> 
> Also, is this a relevant test to do now, or should I wait until there is a session restore issue?

Sorry for the delay. Interesting that you can't find that file... I think you could try it now, keeping in mind if you have created new groups or pinned tabs it'll override those. So its up to you if you want to try it now or wait until this happens again. Although I'm hoping we can tackle an intervention to avoid the need for this in the future (in bug 1906808).

Back to Bug 1983990 Comment 3