Bug: Continue where you left off doesn't always restore tabs

[johnny-poncho]

Description

Problem: After updates to the app, after crashes of the app and sometimes when I don't see an obvious reason for it, Files opens with a clean slate (=the one default tab) instead of those tabs, that were open before the app was closed/crashed.

A save feature to save open tabs to a separate file and reload them later would be useful for those cases.

I asked this on discord before, hoping there would be consideration for that feature to save open tabs, other than the "continue where you left off" function. I was told the continue where you left off feature IS the save option, but it's useless when it doesn't work reliably. Also I was told to send this issue report.

Steps To Reproduce

I don't know what to write other than 1. activate the "continue where you left off"-feature, 2. open a bunch of different tabs, 3. update the app or try to make the app crash and 4. see if it keeps your tabs and reopens them when you restart the app. For me, it doesn't.

Files Version

3.9.1.0

Windows Version

10.0.26100.3194

User ID

09688699-9284-4818-9f21-d4d50dc63b68

Log File

debug.log

[yaira2]

Files automatically restores tabs after updates and crashes. The only scenario I'm aware of where the tab list will not be restored is if you open a second instance of Files and then force close the entire process. This happens because Files only tracks the tabs of the last active instance. We are currently tracking an issue for support of restoring multiple windows. To further investigate this issue, we'll need more details to be able to reproduce the issue you're experiencing.

[johnny-poncho]

Thanks for the explanation. I'll try to make sure to not open a second instance of Files when it crashes and instead force close it directly, then restart it and see if that resolves the problems I had.
Also, I don't know what more details I could provide, probably because it's my first bug report ever.

[yaira2]

Also, I don't know what more details I could provide, probably because it's my first bug report ever.

Let's see if the suggested workaround helps. If it's still an issue, let us know and we'll try to figure this out.