Suspended tabs name with 3 dots and white page (THE PROBLEM IS BACK) #185

Ocel8 · 2022-06-14T18:30:18Z

Extension version: v7.1.6.2
Browser name & version: Chrome Dev. 104.0.5110.0
Browser name & version: Chrome Canary 105.0.5118.3
Operating system & version: Win 10 21H2

The problem is back #161

Same exact problem.

On Chrome stable 102.0.5005.63 and Chrome Beta 103.0.5060.42 is not present, but obviously as soon as the new 104 version will get pushed we will be in trouble.

Civrock1 · 2022-06-17T09:59:24Z

Same here.

Extension version: v7.1.6.2
Chrome Version: 104.0.5110.0 (Official Build) dev (64-bit)

ossilator · 2022-06-17T10:08:07Z

so same procedure as last time: make sure that the chromium team knows about it, and ideally identify the exact commit that caused the regression.

briantully · 2022-06-29T03:48:32Z

Same here.

Extension version: v7.1.6.2
Chrome Version: 104.0.5112.20 (Official Build) beta (arm64)

In terms of "make sure that the chromium team knows about it" — is there a clear, specific process on how to go about doing that? Why would the chromium team care about this extension no longer working?

rapejim · 2022-07-05T07:06:38Z

FYI ... I had the same problem in "Chrome Versión 105.0.5148.2 (Build oficial) dev (64 bits)" but I fixed it by reverting the Tab Scrolling experiment flag (chrome://flags/#scrollable-tabstrip) to Default again (I don't remember enabling it, 🤔)

I didn't say anything, it keeps happening, 😓

kaito0228 · 2022-07-06T06:30:35Z

It has been broken for a couple of weeks now.
I have tried several options and can't find a way to fix it.
Does anyone have any ideas on how to fix it?

Aikatsui · 2022-07-07T15:22:36Z

Does anyone have any ideas on how to fix it?

The problem, suspended page doesn't appear automatically when user go to a particular page and if you click on that page once (somehow if didn't then double click but single click enough) and wait a moment then suspended page will appear; after that you can click again to unsuspend it as usual

(chromium edge build)

mauigirl · 2022-07-17T00:01:22Z

I'm running the same configuration on three different laptops and this problem has just started but on only one of the computers. Which doesn't really make sense because it's a Chrome profile that is synced across all devices. After reading the older linked post I just disabled the Camelizer extension and will see if that helps.
ETA: It didn't help.

mauigirl · 2022-07-18T07:27:06Z

I just realized my problematic Chrome + Marvelous Suspender installation was running Chrome Beta 104.0.5112.48. Have no idea, I don't even remember installing beta in the past but once I removed it and installed a current stable version all is well. Everyone has their proper favicons and names again so it's worth a check to see if you're running Chrome Beta too.

xakraz · 2022-07-18T10:43:57Z

Maybe it is not Chrome Beta that was the isse but the fact that the same Google Profile was used by different versions of Google Chrome and that messed up with the internals of TMS 🤔

I think I face the issue each time after Chrome gets updated and restarts all the windows/tabs.

More over I can confirm @Aikatsui observations: #185 (comment)

if you click on that page once (somehow if didn't then double click but single click enough) and wait a moment then suspended page will appear (after that you can click again to unsuspend it as usual)

I am using Google Chrome Beta on Mac: v104.0.5112.39
And TMS has to manage ~80 suspended tabs

I don't know it all this information might help 🤷🏻

Ocel8 · 2022-07-18T12:06:52Z

Maybe it is not Chrome Beta that was the isse but the fact that the same Google Profile was used by different versions of Google Chrome and that messed up with the internals of TMS 🤔

Nope, I stopped chrome from updating on my laptop, so I still have Chrome stable 102.0.5005.63 and Chrome Beta 103.0.5060.42 and everything works fine, on the desktop I have chrome beta 104 and I have the problem, all with the same account, so it all starts in v104 and as soon as they push it on stable chrome, the bug will be present in every version.

CollinChaffin · 2022-07-22T14:25:23Z

What @Ocel8 said 👆. Has someone already opened an issue with the Chromium team so we can all star it to draw attention? It's making TMS unbearable having to switch to a tab, click on the white page, wait 3+ seconds just for the suspended to appear to then click again to unsuspend it.

briantully · 2022-07-22T15:36:38Z

What @Ocel8 said 👆. Has someone already opened an issue with the Chromium team so we can all star it to draw attention? It's making TMS unbearable having to switch to a tab, click on the white page, wait 3+ seconds just for the suspended to appear to then click again to unsuspend it.

I'd say go ahead and open an issue with the Chromium team. You can do a search to see if a similar issue exists. If not just file a bug and worst case scenario is that if there is a similar issue already filed it will be marked as duplicate.

JarrettGoetz · 2022-08-02T02:25:32Z

Extension version: v7.1.6.2
Browser name & version: Chrome Beta 104.0.5112.79
Operating system & version: Mac OS 12.5

Anyone find any workarounds for this (or hear any responses from reaching out to the Chromium team)? Much appreciated.

PatrickL546 · 2022-08-02T18:26:33Z

Just updated to Google Chrome 104.0.5112.81, It's borked. And here I am again :(

a1termoon · 2022-08-02T20:33:44Z

Just updated to Google Chrome 104.0.5112.81, It's borked. And here I am again :(

same -___-

u1735067 · 2022-08-03T14:04:52Z

If it can help, I'm not using MarvellousSuspender but a cleaned (and not updated) fork of the last Suspender (https://github.com/u1735067/thesuspender) and I'm also affected, I've observed that:

I'm affected since Chrome M104
If I open DevTools on a bugged suspended tab, it automagically fixes it
After enabling logs (maybe not required) and opening the background devtools view, if I switch on a bugged suspended tab, I can see the following log:

WARNING: 1767309385 15:51:29 Could not get internalTabView for suspended tab 
    at Object.initTab (chrome-extension://pbpjlpjdafacbpklfcdkkiehijhcamkh/js/gsSuspendedTab.js:8:15)
    at initialiseSuspendedTab (chrome-extension://pbpjlpjdafacbpklfcdkkiehijhcamkh/js/background.js:889:8)
    at handleSuspendedTabStateChanged (chrome-extension://pbpjlpjdafacbpklfcdkkiehijhcamkh/js/background.js:861:9)
    at chrome-extension://pbpjlpjdafacbpklfcdkkiehijhcamkh/js/background.js:1746:9
gsUtils.js:54 WARNING: 1767309385 15:51:29 TypeError: Cannot read properties of null (reading 'document')
    at Object.initTab (gsSuspendedTab.js:16:13)
    at initialiseSuspendedTab (background.js:889:8)
    at handleSuspendedTabStateChanged (background.js:861:9)
    at background.js:1746:9 
    at chrome-extension://pbpjlpjdafacbpklfcdkkiehijhcamkh/js/background.js:891:17

Also, while I have a LOT of suspended tab (so this bug is really annoying), chrome.extension.getViews() (and chrome.extension.getExtensionTabs()) return a very low count of element (~15 for 200+ suspended tabs), so it looks like Chrome thinks tabs are not attached to the extension?

Edit: filled https://bugs.chromium.org/p/chromium/issues/detail?id=1349787 with those informations

Edit2: now using Marvellous Suspender :)

Edit3: error logs using Marvellous Suspender:

gsUtils.js:54 WARNING: 1767310795 14:16:40 Could not get internalTabView for suspended tab 
    at Object.initTab (chrome-extension://noogafoofpebimajpfpamcfhoaifemoa/js/gsSuspendedTab.js:8:15)
    at initialiseSuspendedTab (chrome-extension://noogafoofpebimajpfpamcfhoaifemoa/js/background.js:885:8)
    at handleSuspendedTabStateChanged (chrome-extension://noogafoofpebimajpfpamcfhoaifemoa/js/background.js:857:9)
    at chrome-extension://noogafoofpebimajpfpamcfhoaifemoa/js/background.js:1723:9
gsUtils.js:54 WARNING: 1767310795 14:16:40 TypeError: Cannot read properties of null (reading 'document')
    at Object.initTab (gsSuspendedTab.js:16:13)
    at initialiseSuspendedTab (background.js:885:8)
    at handleSuspendedTabStateChanged (background.js:857:9)
    at background.js:1723:9 
    at chrome-extension://noogafoofpebimajpfpamcfhoaifemoa/js/background.js:887:17

u1735067 · 2022-08-03T16:57:57Z

Workaround after a browser start or window reopen: Session management -> Old TGS Extension id: put this extension id (noogafoofpebimajpfpamcfhoaifemoa) -> migrate tabs -> this seems to reload all tabs correctly

Technetium1 · 2022-08-04T00:15:52Z

Confirming bug is on Chromium Version 104.0.5112.79 (Official Build) Arch Linux (64-bit), and that @u1735067's temporary solution worked, but only for the 1 active tab per window!

mendelsphotography · 2022-08-04T04:05:50Z

Workaround after a browser start or window reopen: Session management -> Old TGS Extension id: put this extension id (noogafoofpebimajpfpamcfhoaifemoa) -> migrate tabs -> this seems to reload all tabs correctly

thanks @u1735067 , it worked just had the same issue and thought I did something.

u1735067 · 2022-08-08T22:19:09Z

Edit: filled https://bugs.chromium.org/p/chromium/issues/detail?id=1349787 with those informations

It's been reproduced & confirmed by the Chromium team and has been assigned priority 1, so I guess a version fixing this will be released soon :) (cc @gioxx as people seems to be on #188)

tapaolo · 2022-08-08T22:43:24Z

meanwhile, as posted on the bug portal, you can start chrome with --disable-features=AvoidEarlyExtensionScriptContextCreation command line arg as an emergency fix. I tested it and now the extension is working back again.

mendelsphotography · 2022-08-08T23:21:27Z

meanwhile, as posted on the bug portal, you can start chrome with --disable-features=AvoidEarlyExtensionScriptContextCreation command line arg as an emergency fix. I tested it and now the extension is working back again.

Figured it out you have to open the folder where chrome.exe lives in (on windows (C:\Program Files\Google\Chrome\Application)) and then open cmd or PowerShell in there and then run .\chrome.exe --disable-features=AvoidEarlyExtensionScriptContextCreation
btw if you use Chrome shortcut just go to the shortcut and then properties and add the following code after the closing " add a space then --disable-features=AvoidEarlyExtensionScriptContextCreation

Technetium1 · 2022-08-09T01:38:07Z

On Linux you can create a temporarily modified shortcut by copying the default one, making it executable, and changing the exec line. You can change chromium depending on your version (ex: google-chrome-beta)
cp /usr/share/applications/chromium.desktop ~/Desktop/ && chmod +x ~/chromium.desktop && nano ~/chromium.desktop
Then edit Exec line to match: Exec=/usr/bin/chromium --disable-features=AvoidEarlyExtensionScriptContextCreation %U

mkubenka · 2022-08-09T11:20:51Z

On macOS you quit Chrome and run in Terminal:

open -na "Google Chrome" --args --disable-features=AvoidEarlyExtensionScriptContextCreation

potto007 · 2022-08-09T14:51:19Z

On macOS you quit Chrome and run in Terminal:
open -na "Google Chrome" --args --disable-features=AvoidEarlyExtensionScriptContextCreation

Taking it one step further, I made it into an Applescript Bundle:

Launch Script Editor [in Applications/Utilities] & make a new script...

do shell script "\"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome\" --args --disable-features=AvoidEarlyExtensionScriptContextCreation > /dev/null 2>&1 &"
quit

Save your script:

[File->Save] Save it somewhere like ~/Documents as something memorable like "Chrome Suspender"
Make it executable:
[File->Export] Select where to make the script's application bundle, like ~/Applications (your local user rather than system-wide)
Change "File Format" to "Application"
leave all three checkboxes empty
Code Sign: "Sign to Run Locally"
Click Save
Quit Script Editor
Run your script application bundle to open Chrome

Allen-Kwan · 2022-08-09T19:11:05Z

meanwhile, as posted on the bug portal, you can start chrome with --disable-features=AvoidEarlyExtensionScriptContextCreation command line arg as an emergency fix. I tested it and now the extension is working back again.

This works, but I'm just curious - what's happening with Chrome that is breaking it?

briantully · 2022-08-09T22:24:25Z

meanwhile, as posted on the bug portal, you can start chrome with --disable-features=AvoidEarlyExtensionScriptContextCreation command line arg as an emergency fix. I tested it and now the extension is working back again.

This works, but I'm just curious - what's happening with Chrome that is breaking it?

well it's disabling the feature "AvoidEarlyExtensionScriptContextCreation", so my guess is that is what is happening with Chrome that is breaking it.

https://www.google.com/search?q=AvoidEarlyExtensionScriptContextCreation

Masamune3210 · 2022-08-09T22:57:24Z

Basically, Chrome moved extension startup earlier than it was previously, which can break things as well as slow things down. The flag tells Chrome to start extensions later

Allen-Kwan · 2022-08-10T02:41:18Z

Ah, interesting that something like that would be enough to do that - but I'm glad there's a relatively easy fix.

shinmai · 2022-08-10T06:22:02Z

Basically, Chrome moved extension startup earlier than it was previously, which can break things as well as slow things down. The flag tells Chrome to start extensions later.

The command-line flag specifically disables a feature called AvoidEarlyExtensionScriptContextCreation, so surely it's the opposite and parts of Chrome's extension initialisation were moved to happen later (assuming to save on resources by not allocating stuff for extension script contexts when the extensions aren't being used yet), and disabling the feature makes Chrome revert to creating the script contexts earler?

Masamune3210 · 2022-08-10T07:02:19Z

You are correct, I misread the docs lol

fddn · 2022-08-10T07:27:25Z

For windows user if the same problem occurs, add --disable-features=AvoidEarlyExtensionScriptContextCreation to the shortcut, also can be added to the taskbar pinned icons as well.

Right click on the pinned icon -> in the context menu of the icon -> right click on the name of the program -> properties -> add the flag to the Target field -> save and restart the browser the extension starts to work again as it used to.

crxed9 · 2022-08-10T20:17:43Z

Chromium fixed the issue, how long does it usually take for Chrome to get the same update?

Technetium1 · 2022-08-11T02:51:49Z

@crxed9 it varies, but Chrome usually follows in very short order! Can you please mention the version it's fixed in? You can correlate that version with the upstream Chromium they specify here: https://chromereleases.googleblog.com/

gentzel · 2022-08-11T05:38:37Z

Is there a way to disable AvoidEarlyExtensionScriptContextCreation in Chrome OS?

Technetium1 · 2022-08-11T08:07:30Z

@gentzel from https://www.chromium.org/developers/how-tos/run-chromium-with-flags/. it's not something that the average user might want to do.

Chrome OS
Put the device into dev mode, disable rootfs verification, and bring up a command prompt.
Modify /etc/chrome_dev.conf (read the comments in the file for more details).
Restart the UI via: sudo restart ui

tuqqo · 2022-08-11T12:03:29Z

is "AvoidEarlyExtensionScriptContextCreation" bound to a specific set of functions which this suspender extension is using, or can it affect also any other plugin? im asking because i have another strange problem in chrome which is only happening in normal mode and not incognito. so i assume it is also extension based. disabling extensions 1by1 while having chrome open does not fix this other problem. so i wonder if it is safe to just let "AvoidEarlyExtensionScriptContextCreation" disabled, since some of the addons im using might not be updated for some time.

RyukSniper · 2022-08-11T14:54:31Z

Extension version: v7.1.6.2
Browser name & version: Brave [Versione 1.42.88 Chromium: 104.0.5112.81 (Build ufficiale) (a 64 bit)]
Browser name & version: Chrome Canary 105.0.5118.3
Operating system & version: Win 11
The same problem and even with the flag i am always having the same problem

crxed9 · 2022-08-11T16:06:02Z

@Technetium1 it was mentioned as fixed here:
https://bugs.chromium.org/p/chromium/issues/detail?id=1349787

"Verified the fix on latest beta #105.0.5195.28"

CollinChaffin · 2022-08-15T14:16:32Z

Yep chrome just updated few days ago and it's fixed, but now there's a new pending update I'm terrified to update again LOL.

EDIT: Version 106.0.5216.6 (Official Build) dev (64-bit) is working properly

EDIT2: Updated again and Version 106.0.5231.2 (Official Build) dev (64-bit) is still working properly!

medlir · 2022-08-15T16:46:15Z

I'm still at Version 104.0.5112.81 (Official Build) (64-bit). The same as this, but now it's fixed without updating. WHAT?

They may have rolled out a live change to the default value of the feature flag to turn it off without releasing a new build. One of the benefits of using feature flags is they can target multiple versions of the browser and percentages of the existing browser population to roll it out to, and update feature of live browsers. They do it for slow-rolling out new features as well, and one person will pick it up and another won't depending on how they do the roll out and if they're targeting 100% or not.

tapaolo · 2022-08-18T17:09:37Z

Just updated to v104.0.5112.102 and now is working correctly. I noticed is now a little bit slower than before to show all the previews and titles of suspended tabs

pierswalter · 2022-09-01T17:14:36Z

FYI: I've updated Chrome and can confirm that this problem no longer seems to occur with Chrome 105.0.5195.52 on macOS.

voidifdetachd · 2022-10-03T04:17:00Z

On Linux, and was seeing this with 105.0.5195.102-1, but could start chromium in the background with the --disable-features=AvoidEarlyExtensionScriptContextCreation & and it would fix it. Unfortunately with v106.0.x AvoidEarlyExtensionScriptContextCreation doesn't seem to work, nor did launching normally, so had to revert.

CodeWithShreyans · 2023-03-02T14:29:22Z

Haven't experienced this in a long while so seems that it's fixed like others are saying

inside83 · 2023-08-04T17:09:54Z

For windows user if the same problem occurs, add --disable-features=AvoidEarlyExtensionScriptContextCreation to the shortcut, also can be added to the taskbar pinned icons as well.

Right click on the pinned icon -> in the context menu of the icon -> right click on the name of the program -> properties -> add the flag to the Target field -> save and restart the browser the extension starts to work again as it used to.

Using Chrome Version 115.0.5790.171 (Official Build) (64-bit) on Windows 10 with The Marvellous Suspender v7.1.6.2 and adding --disable-features=AvoidEarlyExtensionScriptContextCreation to both taskbar and desktop shortcut does nothing 🤷‍♂️

Anyone has a workaround?

Technetium1 · 2023-08-07T03:15:29Z

Can't replicate this with Chrome Version 115.0.5790.171 (Official Build) (64-bit) on Windows 11.

Technetium1 mentioned this issue Aug 4, 2022

this plugin was broken with the last update of Chrome #188

Open

Technetium1 mentioned this issue Aug 10, 2022

Favicon and title missing from suspended tabs after starting computer #189

Closed

mendelsphotography mentioned this issue Aug 10, 2022

Función "Not Now" No funciona. #186

Closed

gioxx self-assigned this Aug 17, 2022

gioxx pinned this issue Aug 18, 2022

pa-jberanek mentioned this issue Sep 29, 2022

Marvelloous Suspender dosen't work after Chrome updates in August 2022 greatsuspender/thegreatsuspender#1356

Open

Suspended tabs name with 3 dots and white page (THE PROBLEM IS BACK) #185

Suspended tabs name with 3 dots and white page (THE PROBLEM IS BACK) #185

Comments

Ocel8 commented Jun 14, 2022

Civrock1 commented Jun 17, 2022

ossilator commented Jun 17, 2022

briantully commented Jun 29, 2022

rapejim commented Jul 5, 2022 • edited Loading

kaito0228 commented Jul 6, 2022

Aikatsui commented Jul 7, 2022 • edited Loading

mauigirl commented Jul 17, 2022 • edited Loading

mauigirl commented Jul 18, 2022

xakraz commented Jul 18, 2022

Ocel8 commented Jul 18, 2022

CollinChaffin commented Jul 22, 2022

briantully commented Jul 22, 2022

JarrettGoetz commented Aug 2, 2022

PatrickL546 commented Aug 2, 2022

a1termoon commented Aug 2, 2022

u1735067 commented Aug 3, 2022 • edited Loading

u1735067 commented Aug 3, 2022

Technetium1 commented Aug 4, 2022 • edited Loading

mendelsphotography commented Aug 4, 2022 • edited Loading

u1735067 commented Aug 8, 2022

tapaolo commented Aug 8, 2022

mendelsphotography commented Aug 8, 2022 • edited Loading

Technetium1 commented Aug 9, 2022 • edited Loading

mkubenka commented Aug 9, 2022

potto007 commented Aug 9, 2022

Allen-Kwan commented Aug 9, 2022

briantully commented Aug 9, 2022

Masamune3210 commented Aug 9, 2022

Allen-Kwan commented Aug 10, 2022

shinmai commented Aug 10, 2022

Masamune3210 commented Aug 10, 2022

fddn commented Aug 10, 2022

crxed9 commented Aug 10, 2022

Technetium1 commented Aug 11, 2022

gentzel commented Aug 11, 2022

Technetium1 commented Aug 11, 2022

tuqqo commented Aug 11, 2022 • edited Loading

RyukSniper commented Aug 11, 2022

crxed9 commented Aug 11, 2022 • edited Loading

CollinChaffin commented Aug 15, 2022 • edited Loading

medlir commented Aug 15, 2022 • edited Loading

tapaolo commented Aug 18, 2022

pierswalter commented Sep 1, 2022

voidifdetachd commented Oct 3, 2022

CodeWithShreyans commented Mar 2, 2023

inside83 commented Aug 4, 2023

Technetium1 commented Aug 7, 2023

rapejim commented Jul 5, 2022 •

edited

Loading

Aikatsui commented Jul 7, 2022 •

edited

Loading

mauigirl commented Jul 17, 2022 •

edited

Loading

u1735067 commented Aug 3, 2022 •

edited

Loading

Technetium1 commented Aug 4, 2022 •

edited

Loading

mendelsphotography commented Aug 4, 2022 •

edited

Loading

mendelsphotography commented Aug 8, 2022 •

edited

Loading

Technetium1 commented Aug 9, 2022 •

edited

Loading

tuqqo commented Aug 11, 2022 •

edited

Loading

crxed9 commented Aug 11, 2022 •

edited

Loading

CollinChaffin commented Aug 15, 2022 •

edited

Loading

medlir commented Aug 15, 2022 •

edited

Loading