+1
Fixed

Upon browser restart pinned tabs get hibernated, and awake duplicates are created alongside

Zorael 8 years ago updated by Joel Thornton 8 years ago 1
Kubuntu linux 12.10 alpha 3, running Chromium 2.0.1229.6 (r151414). Sidewise version is up to date as of 12-08-23 and its version is listed as 2012.8.14.0.

I always keep a pinned tab of gmail and Google Reader, and I have set Chromium up to save and restore tabs inbetween browser sessions. However, when starting up again Sidebar lists both those pinned tabs twice; one is the original tab but now hibernated, and the other is a new non-hibernated duplicate.

The original tabs inherit branches.

 

Answer

Answer
Fixed

This should now be working properly in 2012.10.18.1 release.

Planned

Definitely a bug and not working as intended. Marking as a planned fix for the near future.

I experience something similar to this on occasion when opening Chrome (using the setting to "restore last session"). It doesn't happen every time it seems, but once in a while on opening Chrome, some tabs (not pinned ones) will be hibernated when they were not previously hibernated, but will also get duplicated in non-hibernated form. 


Clicking on the hibernated one will open a new tab, while clicking on the duplicate will switch to the tab that was open from the last session already.


Chrome 21.0.1180.89 m

Windows 7 x64

Started

I wasn't able to reproduce this bug on Win7/Chrome m21, but I have made a change which I believe will proactively address it on your system: when Sidewise tries to reassociate an opening tab with some hibernated tab in the tree it will no longer require the "pinned" state of the two to be the same.

My suspicion is that the build of Chromium you are using isn't reporting the "pinned" state accurately for tabs as they are opened up. By ignoring "pinned" during the association process, this should likely correct the problem.

I'll update here when this change is released, and if you can test at that point to make sure the fix worked that would be great.

Answer
Fixed

This should now be working properly in 2012.10.18.1 release.