zeniko wrote:...make sure that you're correctly killing SeaMonkey in the first place...on Windows, you'll have to use the Processes tab of the Task Manager...
Yup, that's what I was doing...so it doesn't get a WM_CLOSE.
zeniko wrote:You could indeed try a clean profile first, but if that doesn't cut it, a clean installation of SeaMonkey itself might still make a difference...
After upgrading to Seamonkey 1.1 Beta I noticed it had broke again. On restart, only the last window open was getting restored, which I believe is behavior attributable to the "Last page visited" on startup setting. Indeed this time I could see that the crashrecovery.dat file was not being updated.
Is it expected that extensions need to be reinstalled as Seamonkey is upgraded? (It was installed in the same directory.)
I figured this would be a good time to run the tests on a clean profile, so I created one, reinstalled Crash Recovery, ran some tests, and it worked fine. Now with Crash Recovery reinstalled, I returned to my original profile, and it too was working fine. So it was either a problem with 1.0 or some other odd anomaly that got reset along the way by the browser upgrade and Crash Recovery reinstallation.
zeniko wrote:BTW: I've just now made the test with the latest SeaMonkey 1.1 nightly -- and Crash Recovery still works as expected...
Confirmed. (Well...I was using the beta milestone, rather than a nightly.)
-Tom