Reopening closed tab is non-maximized and causes rapid cycling through tabs

[midluk]

Since 4c2345cfe5a38b744004b2392532fe1934eebeb4 reopening a closed tab causes this tab to be reopened non-maximized. Afterwards otter seems to rapidly cycle through all tabs (some flickering in the window and the window title changes rapidly). The only way to get into a usable state again is to restart otter.

1. Open two tabs with some webpages
2. close one tab
3. reopen closed tab 4 observe problems

This is likely related to #1494 (but that bug has existed before). After "arrange -> Cascade" has been selected for a single open tab (multiple open tabs cause #1494), further reopened tabs are properly opened maximized and without flickering/cycling.

[beastie1]

This is quite annoying, yes. The only workaround I've found is to minimize the window. The flickering and freezing stops and Otter then works fine again.

[ghost]

This workaround does not work for me. Otter crashes after cycling around for a while. Closed tabs and windows is unusable here.

Linux, Otter devel

[vbr]

Hi, it seems this issue with cycling tabs and potentially hanging or crashing the browser is somehow connected with a similar buggy behaviour in other circumstances. I occasionally see this while restoring tabs on program start (or via saved session), as mentioned here, but it can also be triggered in usual browsing which involves opening an webpage in a new tab (from a link or via scripting) as mentioned in: https://github.com/OtterBrowser/otter-browser/issues/1544

I also noticed these cycling tabs after arranging the tabs (from the context menu of the tabbar) - e.g. Maximize all. I couldn't find a clear pattern for "reliably" simulating this behaviour, but is seems to involve rather heavier pages, which take some tome to load or which are more "active" or are (trying to be) responsive via scripting etc.

Fortunately, the mentioned workaround using minimize of the program window and restoring it seems to work for me for all cases sofar, the minimize button remains usable and responsive. Thanks for sharing that! I wonder, whether this could be utilised programmatically to solve (or hide the symptoms of) this bug - e.g. issuing these events after detecting the massive cycling (if it is doable...)

(Using Otter 64bit webkitNG, 1.0.81 weekly 272, Win 7p.)

vbr

[beastie1]

Has anyone tested this lately?

[Frenzie]

On Windows or in general? I don't think I can/could repro it in Linux as per the OP but maybe I missed a step.

[beastie1]

Unfortunately I can't test it on my FreeBSD system right now. But I tested it recently on Windows using the latest weekly build and the bug seems to be gone, which is why I wanted someone to confirm either way.

I don't think you could've missed that one. It is (was?) way too frequent, obvious and annoying hehe ;)

[midluk]

I also can't reproduce this bug any more with current git master a6f985e33 on Fedora 30.

[aurhat]

I can't reproduce the bug when I open new links. I can reproduce it only when I minimize/maximize tabs manually.