Ping Cha, good news but strange news about SM.

Hey guy, and everyone else,

More interesting stuff about Session Manager.

I have it set to save the session every N minutes, and it will do that
for hours, but periodically it stops and only saves 77-byte files. I
think sometimes it starts up again later, but maybe I've done things
like close FF to make that happen. I think not, but maybe.

****So tonight it starts to slow down, and I go to do File/Exit, but I
forgot that I'd been monitoring the files and backup-NN.session hadn't
been updated for 2.5 hours. Not only that
C:\users\user\appdata\roaiming\mozilla\firefox\pro files\nnnnnnn.default\sessionstore-backups\recovery.js
and .bak both showed in Search Everything without any length showing.
That's really bad, because often the first one is 77 bytes but the
second one is 3Megs. (Which one is the real backup file? I guess
the first one exists because I checked the box Save Session every N
minutes, but what use does it make of them? If I didnt' say that,
would there only be two or three choicces when it came to restarting
FF? recovery.js, recovery.bak, and maybe previous.js*****?)

So while it's closing, and I don't know how to stop it from closing, I
realize I have no backup that's not 2.5 hours old. And when it's
closed, the new first one is again, 77 bytes. I wait 8 minutes to
see if it gets another copy or the second one2 get a copy with a
length and nothing happens.

Then I start it up again, and I get the almlost full page screen,
(but it doesn't have anything in the upper left corner (and it's only
the top 1/5th of the screen until I pick a session) and at the bottom
right it doesn't say Load, it says Recover, and I've picked either the
first or the second one in the list (sadly, I've already forgotten,
even though it was the right pick) and everything opens up NOT 2.5
hours old, but only 5 minutes old, I think.

And a minute after that both the first and second kind of backup files
get new, full length files.

So if I weren't monitoring the files I woudln't have known there was
reason to worry, but otoh, surely I can't go forever with no backups.

There must be a hidden location where the backup is kept in a temp
file or something, until after FF has been reopened.

Do you know which file is the real backup file, the first or second,
asd in the paragragph above starting with ****


*****Earlier, when I had trouble, I deleted .bak, renamed .js to .bak,
and renamed previous.js (which was 3Meg) to recovery.js. It didn't
help at all, but that was days ago and I see now that I'm still
missing previous.js, even though all 3 exist in the other profile
(which has the same name as this one except .default is .default.P
!!!) I would have though previous would be recreated by now, since
I've seen the other two change their size.

Sorry, that was meant to say Char.

See previous post for text.

On Mon, 23 May 2016 01:37:40 -0400, Micky
wrote:

Hey guy, and everyone else,

On Mon, 23 May 2016 01:37:40 -0400, Micky
wrote:

Hey guy, and everyone else,

More interesting stuff about Session Manager.

I have it set to save the session every N minutes, and it will do that
for hours, but periodically it stops and only saves 77-byte files. I
think sometimes it starts up again later, but maybe I've done things
like close FF to make that happen. I think not, but maybe.

I haven't seen such a thing here, and I have no idea why it's doing that
with you.


****So tonight it starts to slow down, and I go to do File/Exit, but I
forgot that I'd been monitoring the files and backup-NN.session hadn't
been updated for 2.5 hours. Not only that
C:\users\user\appdata\roaiming\mozilla\firefox\pr ofiles\nnnnnnn.default\sessionstore-backups\recovery.js
and .bak both showed in Search Everything without any length showing.
That's really bad, because often the first one is 77 bytes but the
second one is 3Megs. (Which one is the real backup file? I guess
the first one exists because I checked the box Save Session every N
minutes, but what use does it make of them? If I didnt' say that,
would there only be two or three choicces when it came to restarting
FF? recovery.js, recovery.bak, and maybe previous.js*****?)

So while it's closing, and I don't know how to stop it from closing, I
realize I have no backup that's not 2.5 hours old. And when it's
closed, the new first one is again, 77 bytes. I wait 8 minutes to
see if it gets another copy or the second one2 get a copy with a
length and nothing happens.

Then I start it up again, and I get the almlost full page screen,
(but it doesn't have anything in the upper left corner (and it's only
the top 1/5th of the screen until I pick a session) and at the bottom
right it doesn't say Load, it says Recover, and I've picked either the
first or the second one in the list (sadly, I've already forgotten,
even though it was the right pick) and everything opens up NOT 2.5
hours old, but only 5 minutes old, I think.

And a minute after that both the first and second kind of backup files
get new, full length files.

So if I weren't monitoring the files I woudln't have known there was
reason to worry, but otoh, surely I can't go forever with no backups.

There must be a hidden location where the backup is kept in a temp
file or something, until after FF has been reopened.

Do you know which file is the real backup file, the first or second,
asd in the paragragph above starting with ****


*****Earlier, when I had trouble, I deleted .bak, renamed .js to .bak,
and renamed previous.js (which was 3Meg) to recovery.js. It didn't
help at all, but that was days ago and I see now that I'm still
missing previous.js, even though all 3 exist in the other profile
(which has the same name as this one except .default is .default.P
!!!) I would have though previous would be recreated by now, since
I've seen the other two change their size.

I honestly have no idea why you're doing what you're doing. I've never had
the urge to monitor Firefox files and their timestamps and respective sizes.

More to the point, now that you're using Session Manager, I have no idea why
you're still messing around with the files that Firefox uses to restore the
last session. Why not just enjoy what Session Manager can do?

--

Char Jackson

On Mon, 23 May 2016 02:03:57 -0500, Char Jackson
wrote:

On Mon, 23 May 2016 01:37:40 -0400, Micky
wrote:

Hey guy, and everyone else,

More interesting stuff about Session Manager.

I have it set to save the session every N minutes, and it will do that
for hours, but periodically it stops and only saves 77-byte files. I
think sometimes it starts up again later, but maybe I've done things
like close FF to make that happen. I think not, but maybe.

I haven't seen such a thing here, and I have no idea why it's doing that
with you.


****So tonight it starts to slow down, and I go to do File/Exit, but I
forgot that I'd been monitoring the files and backup-NN.session hadn't
been updated for 2.5 hours. Not only that
C:\users\user\appdata\roaiming\mozilla\firefox\p rofiles\nnnnnnn.default\sessionstore-backups\recovery.js
and .bak both showed in Search Everything without any length showing.
That's really bad, because often the first one is 77 bytes but the
second one is 3Megs. (Which one is the real backup file? I guess
the first one exists because I checked the box Save Session every N
minutes, but what use does it make of them? If I didnt' say that,
would there only be two or three choicces when it came to restarting
FF? recovery.js, recovery.bak, and maybe previous.js*****?)

So while it's closing, and I don't know how to stop it from closing, I
realize I have no backup that's not 2.5 hours old. And when it's
closed, the new first one is again, 77 bytes. I wait 8 minutes to
see if it gets another copy or the second one2 get a copy with a
length and nothing happens.

Then I start it up again, and I get the almlost full page screen,
(but it doesn't have anything in the upper left corner (and it's only
the top 1/5th of the screen until I pick a session) and at the bottom
right it doesn't say Load, it says Recover, and I've picked either the
first or the second one in the list (sadly, I've already forgotten,
even though it was the right pick) and everything opens up NOT 2.5
hours old, but only 5 minutes old, I think.

And a minute after that both the first and second kind of backup files
get new, full length files.

So if I weren't monitoring the files I woudln't have known there was
reason to worry, but otoh, surely I can't go forever with no backups.

There must be a hidden location where the backup is kept in a temp
file or something, until after FF has been reopened.

Do you know which file is the real backup file, the first or second,
asd in the paragragph above starting with ****


*****Earlier, when I had trouble, I deleted .bak, renamed .js to .bak,
and renamed previous.js (which was 3Meg) to recovery.js. It didn't
help at all, but that was days ago and I see now that I'm still
missing previous.js, even though all 3 exist in the other profile
(which has the same name as this one except .default is .default.P
!!!) I would have though previous would be recreated by now, since
I've seen the other two change their size.

I honestly have no idea why you're doing what you're doing. I've never had

To try to predict whether it is safe to close FF or not, without
losing tabs.

the urge to monitor Firefox files and their timestamps and respective sizes.

More to the point, now that you're using Session Manager, I have no idea why
you're still messing around with the files that Firefox uses to restore the
last session. Why not just enjoy what Session Manager can do?

Because it doesn't always do it. Because at least on one occasion, it
forgot all the tabs, and on another it forgot recent ones. And if I
complain to the author or on other boards, I want to give as much info
as possible.

Again today, after no trouble since I woke from its sleep 3.5 hours
ago, starting 50 minutes ago, attempts to write backup files started
failing. How can it possibly restore tabs I've opened since then,
unles there is some hidden location where it has inded saved the info?

This time I was very careful to open only one old tab per window (4
windows. Two windows I haven't even gone to, so many no tab has been
loaded there.) And to close as many new tabs as I can, striving to
close all but the first one, on theory that closing tabs in the middle
doesn't free up their RAM, although I don't really think contiguity
has anything to do with it.