Tree structure and hibernated tabs lost sometimes on startup

[Wizek]

In the past 3-4 weeks I noticed that my entire session is wiped out sometimes when I start chrome.

The first time I lost ~1100 hibernated tabs that accumulated in the past months. It was frustrating, but hey, at least Sidewise got noticeably faster due to the lesser load.

Yesterday it happened again, and here is what I noticed: my computer overheated so it was an instant and unexpected shut-down. When booting back up, chrome asked me whether to restore the previous open tabs, and sidewise only displayed those, forgetting about all the hibernated ones, the tree structure relations of the open ones, highlights or folders.

In the options, I have these set to true:

• Remember open tabs between browser sessions
• Automatically collapse Last Session windows on start-up

[Wizek]

Update: Even if I cleanly exit ("Wrench" menu > Exit) Chrome, all my Sidewise data seems to get lost just as I described above.

Except for the handful open tabs which chrome takes note of.

@joelpt Do you have any idea what might cause this?

[joelpt]

I can't seem to reproduce this problem here. That being said, I think some changes in my latest dev build may correct what I'm guessing is causing this.

Would you be interested in running the dev build to see if it corrects the problem? It sounds like you have an easily reproducible case on your system.

[Wizek]

Yeah the next time I boot up my Windows OS I'll give it a shot. Is there a specific revision I should test with?

[joelpt]

I've just released a hotfix for this problem. If you can still reproduce this problem, can you update Sidewise and see if this fixes your problem?

Related Userecho thread: http://sidewise.userecho.com/topic/145990-lost-all-hibernated-tabs-and-folders-on-reboot/ Changelog: http://www.sidewise.info/changelog/

[Wizek]

The issue remains on my Windows OS: http://screencast.com/t/oUOyFbXnOv8z

[joelpt]

Thank you for the screencast, very helpful in understanding the situation. Very strange behavior! It looks like the tree isn't even being saved/loaded at all.

Could you please do the following? This will hopefully narrow down the problem to the specific cause, or at least help me see whether the problem is happening before or after the Chrome restart.

• Try opening a new Chrome window, then hibernate that whole window via a right click on its window row in the tree.
• Wait about 15 seconds, then restart Chrome. When Chrome comes back up, is that hibernated window still in the tree?
• In Sidewise Options/Advanced, turn on "Enable diagnostics"
• Do the "open two new tabs then hibernate them" as you did in your screencast
• In Sidewise Options click the "Send diagnostic report" button and state this is the "before restart" diagnostic log in the submission title
• Restart Chrome
• In Sidewise Options click the "Send diagnostic report" button and state this is the "after restart" diagnostic log in the submission title

Thanks so much for your help diagnosing this one. With a little luck the above information will be enough to track down what's going awry here.

[Wizek]

When Chrome comes back up, is that hibernated window still in the tree?

No, it is gone.

Sent you the diagnostics.

[joelpt]

Thanks for the report. Stranger and stranger ...

Unfortunately I didn't get enough from the logs to nail down the cause. But it is strange - in your "after restart" log, most of the usual startup-time diagnostic information is simply not there. Did you by chance turn off "Enable diagnostics" before the restart and turn it back on after? If so that would explain the missing info in the second log, which may tell me more about the primary issue.

If you didn't turn it off, I'm currently stumped as to what could be causing this problem. Though it would lead me to think the empty-tree issue and the missing-log issue could be caused by the same underlying bug.

I am planning on publishing a "Sidewise Early Release" build soon (probably next week). When that is ready would you be interested in trying it and seeing if this problem persists for you there? That new build has some changes to how Sidewise handles Chrome shutdown that may address the issue; failing that, I have also improved the diagnostics to capture more information.

[Wizek]

Did you by chance turn off "Enable diagnostics" before the restart and turn it back on after?

Well, I didn't turn the diagnostics off, it was off when I started chrome back again, and turned it on to be able to send you the logs. I guess it doesn't save the the settings either.

[Wizek]

I am planning on publishing a "Sidewise Early Release" build soon (probably next week). When that is ready would you be interested in trying it and seeing if this problem persists for you there?

Sure.