Sometimes Sumatra does not remember opened documents, opens empty. Not sure why, probably during PC shutdown, restart. If I just open, close - it remembers.
Exactly. This can happen when
1: The computer suffered an unexpected shutdown (BSOD, forced shutdown by power button, ...)
2: The files you had opened were temporarily saved to a temp folder (like when they're "opened from browser" like shown here: https://imgur.com/0JvUpNe ) Those files seems to disappear after unexpected shutdowns for example (at least happens on my Win. 7 x64 system).
I opened two tickets to air suggestions/possible workarounds, but they were closed due to what I think were misunderstandings:
https://github.com/sumatrapdfreader/sumatrapdf/issues/452 Here I should have said temp folder and elaborated further.
https://github.com/sumatrapdfreader/sumatrapdf/issues/451
Hope the issue can be fixed some way -- it would be nice to have robust "session" or "remember" functionality.
Same problem here - after a forced reboot of some installer (didn't asked for unsaved files) no tabs were remembered after the reboot.
I also noticed that when I have only one tab open, it will not be remembered, only when there are at least two tabs open.
I have similar problem, but much worser. Last opened documents are saved ONLY if I exit using File-Exit command. Closing window with [X] causes start from empty page. Same with windows shutdown etc.
All PDFs are opened from local hard drive folder (not temporary). SumatraPDF version 3.1.1 64-bit, OS: Windows 7 Pro x64.
Correction: it does not remember opened document only if single document was opened. Two or more documents remembered correctly.
Does not depend of number of openned documents. I always have few documents
ะก ะัะฑะพะฒัั,
ะะปะตะบัะตะน.
Blessings,
Aleksey.
2016-03-28 15:29 GMT+03:00 Denis [email protected]:
Correction: it does not remember opened document only if single document
was opened. Two or more documents remembered correctly.โ
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/sumatrapdfreader/sumatrapdf/issues/458#issuecomment-202364756
I have this issue as well. Open documents are only remembered if there is more than one open.
for me too it remembers openend pdf only when two o more (win10 x64)
The odd part about the session loss is that it doesn't even remember the _previously loaded_ session. That is, if you close SumatraPDF normally and then reopen it, it remembers the session. So it must have loaded that from somewhere. Yet if it closes abnormally, I don't necessarily expect ti to remember changes I made in that session.
But there's no excuse for it not loading the old session data that it previously loaded.
Update on this? @kjk
The issue of not remembering due to windows reboot should be fixed.
Not reopening when there was only 1 document opened is expected behavior.
Last opened documents are saved ONLY if I exit using File-Exit command. Closing window with [X] causes start from empty page.
This is should be fixed to behave the same way, no?
Not reopening when there was only 1 document opened is expected behavior.
I didn't expect it and was just trying to find out why RememberOpenedFiles doesn't work until I landed here... At least there should be some comment in the settings or SumatraPDF-settings.txt to avoid confusion.
I exit using File-Exit command but unfortunately Last opened documents are not saved!
I use latest version, and yes I have RememberOpenedFiles=true.
@csengh Ensure that in advanced options
RestoreSession = true
Then when TWO or more windows or tabs in a session are closed they will open when restarting SumatraPDF by opening any one of them or even another, beware this can be affected by dual or more sessions since if any session has only one file open in each window it will not meet the two or more per session criteria.
Oh Yeah, resolved!
Thank you very much!
if any session has only one file open in each window it will not meet the two or more per session criteria.
That's a bug and should be fixed.
Most helpful comment
That's a bug and should be fixed.