restore session not working as expected (CB 4.0.9.102) - Printable Version +- CentBrowser Forum (https://www.centbrowser.net/en) +-- Forum: Product Related (https://www.centbrowser.net/en/forumdisplay.php?fid=1) +--- Forum: Bugs & Suggestions (https://www.centbrowser.net/en/forumdisplay.php?fid=4) +--- Thread: restore session not working as expected (CB 4.0.9.102) (/showthread.php?tid=2812)

restore session not working as expected (CB 4.0.9.102) - badablek - 05-31-2019 Hi Centbrowser team, since the new 4.x revision of CentBrowser, disabling lazy session loading does not work as expected, when used with the restore session option. Normal behavior : All tabs are restored and FULLY loaded at launch. It works fine under 3.9.2.45 and below. Bad behavior (since 4.0.9.102) : CentBrowser only loads 4 tabs (active tab + the 3 tabs that were opened after the active one), all other tabs are not loaded until you click on it (title is in italic, which stand for : not loaded at all, please click on me to load !) Tested with 32 and 64bit versions, portable or not, in normal and safe mode, with and without extensions or tweaks (the only "tweaks" : restore session + disable lazy session). I also tried by updating a portable CB 3.9.2.45 to 4.0.9.102, so it loads exactly the same tabs with the same websites, with the same extensions. Was working under 3.9.2.45, not working with 4.0.9.102 You can see this behavior by yourself quite easily : choose "Restore session", disable "lazy session loading". Open up more than 4 tabs, close CB, and relaunch it. You will see that CB will fully load only 4 tabs. The others will stay in italic, unloaded, until you click on it. Can you confirm this bug and, please, kill it ! A browser is absolutely useless if you can't fully load ALL YOUR TABS at launch (lazy session loading is quite uninteresting IMHO) Thanks. ps : the exact english names of "Restore session" and "lazy loading" may differ at little bit...as I'm using the french translation. RE: restore session not working as expected (CB 4.0.9.102) - Admini - 06-01-2019 Thanks for the feedback. We will fix this and increase version number again.