Tabby uses excessive time to load session

[Musee "lae" Ullah]

With >500 tabs open, it can take several minutes to populate the tab bar on open before the most recently used tabs show up. This is a regression from pre-Tabby.

Midori 0.5.5~r6395 ((null))
GTK+ 2.24.20 (2.24.20) Glib 2.36.4 (2.36.4)
WebKitGTK+ 1.10.2 (1.10.2) libSoup 2.42.2
cairo 1.12.16 (1.12.16) libnotify 0.7.5
gcr No granite No
Platform X11; Linux x86_64
Identification Mozilla/5.0 (X11; Linux) AppleWebKit/537.6 (KHTML, like Gecko) Chrome/18.0.1025.133 Safari/537.6 Midori/0.5
Video Formats H264 [x] Ogg Theora [x] WebM [x]

[André Stösel (ivaldi)]

There is already a branch which implements this feature.
(your feedback is welcome)

[Musee "lae" Ullah (sleepingkyoto)]

I should probably clarify that I meant this bug as an issue of startup time, not about the order that tabs are reopened. It takes about 4-7 minutes for Midori/Tabby to finish populating - when I would expect all tabs to be populated instantly.

[André Stösel (ivaldi)]

The general idea of tabby is to delay session restoring in order to
avoid a frozen gui. Tabby accomplish this by limiting the number of
tabs it restores at a time. -> It will be always slower then the
pre-tabby version, but now you can actually use midori while the
session will be restored.
Another feature of tabby is that it restores tabs in order of last
usage -> ideally it shouldn't matter how long it takes to restore the
complete session because the probability you need a tab decreases with
it's "age" (time of last visit).

However, at the time when I defined the number of tabs to restore at a
time, the delayed loading feature didn't work -> I guess we can
increase the limit -> please test lp:~ivaldi/midori/tabby-restore-count