Problems in latest Windows build - bug collection

[Sa-Ja-Di]

When i try to open a new tab from a page with a link - either with middle click or open in new tab, the tab is full sized and no small window.

Using latest Windows 64 bit build.

[Sa-Ja-Di]

Also, tabs still jumping around when i open the browser and load all my tabs of my session.

Not broken way should be, that when i scroll trough the tab list, the focus should stay at the right now activated tab.

Right now it's that the focus jumps around between loading tabs, as long as tabs are loading, then, focus is again on the last activated tab of my session.

[Sa-Ja-Di]

Issue number 3 which is still present is if i click on a link from a third party program and Otter is opening, the browser acts strange and "flashes" - if i close the new opened tab which was opened that way, browser acts normal again.

Would be good to have a little bit more stability under Windows again too, right now the problems are collecting as it seems :(

Last version which worked rather flawless on Windows was this one:

otter-browser-win64-beta12-v2

[Emdek]

@Sa-Ja-Di, behavior of tabs can be only improved as part of #190, trying to change it before switching to new version seems to be waste of resources.

I can confirm that odd regression in MDI.

[Dizirgee]

I discovered otter and got latest (175 x64 win7) version to try and it appears otter eats lots of ram. First I did hit 2GB (with just some tabs, maybe 10?) in office today on work laptop and run out of memory. I tried to close some tabs (down to 2 or so not sure) and memory wasnt realased, it was still sitting at ~2GB And now at home I'm sitting on 12tabs (incl youtube 8min clip) with 750MB private ram usage. When I again close all the tabs down to just this one ram went down only to 605...not sure if working as intended.

PS: also tried to "push" otter up, did open ~35 random tabs and got ram up to 2,3GB closing all but this one leaves 1,7GB (waited one min to see if dealloc just takes time) and 80x threads

btw for issue1 reported here, I dont really undertand what OP meant, when (mid) clicking link it opens properly in another tab.

sry for being a little offtopic perhaps but didnt want to log new issue, and i found one about high ram consumption but its closed already

edit: tools -> preferences -> startup -> continue previous sessions appears not to work? When i close otter and open it anew it starts with blank/homepage

[Emdek]

@Dizirgee, you probably should stick to beta 12, . Are you using QtWebEngine backend? No issues with continuing session here.

[Dizirgee]

tbh dunno, I got otter-browser-win64-weekly175.7z via "other package" link as i dont like installers when not necessary (especially when it asks for admin rights). starting otter-browser.exe, when going Help it shows "About Qt..." , only thing i've changed was language (to english, as i also dont like apps to guess language/translations :) ) so i guess I do use Qtweb?

I tried beta12v2 (otter-browser-win64-beta12-v2.7z) and continuing session works fine, but not on 175.

edit: About otter 175 - webkit backend 602.1 , About Qt - Qt version 5.8.0

[Emdek]

@Dizirgee, the other action, "About Otter". It seems that you are using QtWebKit backend (it's important to use full name since both use the same prefix). Do you have any memory issues with beta?

[Dizirgee]

on beta12 there also seems to be memory issue. Open 30 tabs, 2,6GB ram, close all except last one tab drop to 2GB and <1min later to 1,6GB and it stays there with just this github site open...so some memory is released but to keep 1,6GB for one empty tab seems a lot :) btw I have eset AV running but i guess it shouldnt have impact on memory usage of the app even if its scanning or whatever its doing, nothing else that should interfere with otter process i think.

[Emdek]

@Dizirgee, you can try to set Cache/PagesInMemoryLimit in about:config to 0, but remember, memory not in use is wasted memory. :-D