simple-tab-groups: (1694699) Firefox 86.⋯: conflict with any of six other extensions: loss of tab content after Simple Tab Groups loads a multi-tab group into an additional new window

Overview (postscript)

Apparent conflict with six or more extensions. Not reproducible with Firefox 85.0.2, fixed in Firefox 87.

Jump to:


Description

With Simple Tab Groups, Duplicate Tabs Closer, FoxyTab and (many) other extensions enabled, grouped tabs are:

  • sometimes apparently detected as duplicates; and
  • later, each one of these becomes a ‘New Tab’

– and then if the duplicates (the blanks) are closed, the affected groups become empty (or nearly empty).

As far as I can tell, this problem began after I gained an update to Firefox from 85.0.2 to the first pre-release port to FreeBSD of 86.0.

Reproducibility

I’m struggling to make this consistently reproducible. I aim to do so as soon as possible.

Images

Frames from a screen recording.

1,404 tabs, 111 of which are in the FreeBSD group:

image

109 duplicates, apparently:

image

With the number of duplicates apparently up to 191, after opening other groups into third and fourth windows:

image

After closing the fourth, third and second windows, where previously there were titled duplicates, now it’s a mass of ‘New Tab’:

image

After quitting then reopening Firefox, a click to close the duplicates:

image

– leaving the three recently used groups (Firefox, FreeBSD and helloSystem) almost completely empty:

image

Environment

Simple Tab Groups 4.7

% pkg query '%o %v %R' firefox
www/firefox 86.0,2 FreeBSD
% freebsd-version -kru
14.0-CURRENT
14.0-CURRENT
14.0-CURRENT
% date ; uname -a
Sat 20 Feb 2021 11:17:28 GMT
FreeBSD mowa219-gjp4-8570p 14.0-CURRENT FreeBSD 14.0-CURRENT #14 main-f44e67d120: Wed Feb 10 23:57:02 GMT 2021     root@mowa219-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64
% 

Recently updated extensions:

image

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 35

Most upvoted comments

Firefox 87 fixed

Extension mitigation possibilities for bugged builds of Firefox 86.⋯

… Extensions in the first group cannot easily work around this. …

– this group includes Simple Tab Groups, so I’ll close this issue and look forward to the fix in Firefox.

  1. about:profiles
  2. root directory
  3. open directory
  4. exit Firefox

– then backup the directory (folder) in whatever way you like.

Officially: http://mzl.la/1xKrFsk

Regression in Firefox

▶ Mozilla bug 1694699 - Investigate tabs API regression in Firefox 86

RESOLVED FIXED

88 Branch

I wouldn’t really feel safe after publishing my list of extensions, but also I’m still on 85.0.2 so I don’t know if STG would break by any of the other extensions that I use.

The six extensions that appear to be in conflict with Simple Tab Groups with Firefox 86.0

See above, under https://github.com/Drive4ik/simple-tab-groups/issues/779#issuecomment-782650906 – linked (cross-referenced) issues for five of the six.

Without links, the shortlist:

  • Open in Reader View
  • Refined GitHub
  • Threads for YouTube
  • Translate Web Pages
  • Unskew My Search
  • Want My RSS

Does this mean I’m better quickly change the update method of Firefox to manual? (I already did, just in case) Because 86 has been rolled out today

https://github.com/Drive4ik/simple-tab-groups/issues/779#issuecomment-783606367

Reproducible with version 20.9.10 of Refined GitHub, …

Not reproducible with archaic version 1.19.0 of Refined GitHub – https://addons.mozilla.org/firefox/downloads/file/653773/refined_github-1.19.0-an+fx.xpi

  • from 2017
  • I do not suggest use of so old a version
  • the comparison is for test purposes only.

@Drive4ik and friends hi, here’s a debug log. .json renamed to .json.txt for compatibility with GitHub.

In this case, the bug – with Refined GitHub enabled – was observed in a new window after loading group 100, which comprises eight tabs.

"load-group-100"

  • first appearance at line 2,761 of 3,901
  • second and final appearance at line 3,659

STG-debug-logs.json.txt

  • logged with my very heavily loaded profile.

NB https://github.com/Drive4ik/simple-tab-groups/issues/779#issuecomment-783691509 whilst the issue is consistently reproducible with very few tabs, it is not reproducible with so few tabs whilst debugging is enabled.


Confirmed, for me: the issue is not reproducible with Firefox 85.0.2.

Yesterday I corresponded with someone at Mozilla, they suggested raising a bug there to tell what (if anything) has changed to cause or expose this extensions conflict.

Re: https://www.freshports.org/www/firefox/#history (currently switch to rc2 with reference to https://hg.mozilla.org/releases/mozilla-release/pushloghtml?startdate=2021-02-16&enddate=2021-02-18), it will probably make sense for me to wait until the port to FreeBSD is based on release 86.0 of Firefox.

Re: https://old.reddit.com/r/firefox/comments/loptje/firefox_86_extension_conflicts/go7pmdd/ early indications are that at least one other user, not with FreeBSD, may be affected; “… pretty sure it never happened before 86 beta. …”.

https://github.com/Drive4ik/simple-tab-groups/issues/779#issuecomment-783684125

… probably no loss when quitting Firefox. If users quit more often than they close windows, this might explain why encounters of the issue are not widespread. …"

Debug logging

Initially – with a test profile (very few tabs, probably less than ten)

Whilst the debug feature of Simple Tab Groups 4.7 was enabled:

  • the bug was not reproducible.

After debugging was disabled:

  1. decline the invitation to save the log
  2. the bug became immediately reproducible.

With my everyday profile (1,394 tabs at the time of writing)

With the debug feature of Simple Tab Groups 4.7 enabled:

  • the bug is reproducible …

Reproducible with current version 21.2.19 of Refined GitHub with outdated (previous) version 4.6.2 of Simple Tab Groups.

At this point I realised: probably no loss when quitting Firefox. If users quit more often than they close windows, this might explain why encounters of the issue are not widespread.

Next up: debug logging with the current version.