Basil Chupin said the following on 02/14/2010 08:14 AM:
I think, Basil, you're misreading Michael's response. It a matter of the TIME IT TAKES for FF to write out your current tab settings - to the 'sessionstore.js' file, if I understand correctly. The cache in the sense of the cache of fragments and images is not the concern.
Try just waiting.
And how long is one supposed to wait? One minute? 5 minutes? An hour?
Yes, waiting is frustrating - "a watched pot never boils". I've never timed it but its not been more than a few minutes. Heck, shutting down KDE takes a few minutes as well. Perhaps its waiting for FF and never told me. Personally I find that shut-down time annoying.
Irrespective of how long, or my wife, waits, the error message comes up.
Really? You've waited an hour?
Or slap a watch on the 'sessionstore.js'
"...slap a watch on the 'sessionstore.js'". What exactly is this supposed to mean? :-)
Please explain.
There are many tools to watch files. You can watch for writes, watch for the file to grow in size, whatever, change in its access time. Look at "tail", "ls", "fuser" for some ideas. Think of a few lines of shell. Whatever. I was deliberately vague so as to leave open options. Can we get details of your real time, file sizes and date-stamps, please. Right now this is just a p'ing contest. I've given a description of an area of investigation, and I hope you'll examine it and report back some 'metrics'. Then we can determine if or if not this is related.
Nevertheless, in all the many years that I have been using Firefox (and its predecessor) this problem has NEVER occurred on my, or my wife's, system - until 3.6 -- and maybe until the updates/upgrades to 11.2 which occurred at the same time.
Also, try this. FF needs to save state on a poper shut-down, but its crashed on me and I've been able to start it immediately, whereas I've not been able to start it imediately if I close it. I've had to wait, and seem the sessionstore.js change. So, try crashing FF and see it it will start again immediately. That, at elast, gives us a point of congruence. Don't "shut-down, wait, get frustrated, kill". Kill it to start with. While monitoring sessionstore.js for changes. Then do a close ... while monitoring sessionstore.js for changes. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org