Open Bug 1633648 Opened 4 years ago Updated 1 year ago

pinned Slack tabs sometimes don't restore correctly on startup

Categories

(Firefox :: Session Restore, defect, P4)

Product:
Firefox
Component:
Session Restore
Type:
defect

Tracking

()

Status:
REOPENED
Tracking Flags:
Tracking Status
firefox86 --- wontfix
firefox87 --- wontfix

People

(Reporter: dbaron, Unassigned)

References

Details

(Keywords: regression, Whiteboard: [not-a-fission-bug])

Attachments

(3 files)

Bug1.png
42.16 KB, image/png
Details
screenshot of the first busted slack tab today
37.84 KB, image/png
Details
broken.moz_log
16.78 KB, text/plain
Details

I have a Firefox session with quite a few pinned tabs. 5 of them (currently; has been 6 at some points in the past few months) are Slack instances.

When I restart, occasionally the Slack tabs are restored as a blank tab -- just completely blank contents, blank URL bar, but the correct Slack icon in the URL bar. The back/forward history still works, so the best way to get back to Slack is to hit back or forward -- and then things are normal. (If I hit forward, back will then keep me in a working state with a good URL in the URL bar.)

I run nightly, so generally restart twice a day. I think I've been seeing this a few times a week, though I think the frequency has varied a bit since I started seeing it. I believe the first time I saw it was the evening of January 16, the second time was the morning of February 6th, and it's been a little more frequent but on-and-off since then. It tends to happen either to all 5 Slack tabs at once, or to none of them.

I think when I first started seeing it I may have seen it on some other sites as well, but I don't think that's happened recently.

Note that I didn't get the "new Slack" on any of my 5 or 6 slacks until March 25, so it happened with both old and new Slack.

(When this initially started, there was a discussion in Slack about the bug, but as far as I can tell it didn't get filed, so filing now... sorry!)

The priority flag is not set for this bug.
:mikedeboer, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(mdeboer)

So these kind of bugs are nigh impossible to reproduce and/ or track. The only thing that recently changed that could have an impact as described here is bug 1507287.

Alphan, flagging you to put this on your radar, even though I totally understand that there's probably no action for you here at this point.

Flags: needinfo?(mdeboer) → needinfo?(alchen)
Severity: -- → S3
Priority: -- → P4

I recall a similar bug before.

Flags: needinfo?(alchen)
See Also: → 1548508

(In reply to David Baron :dbaron: 🏴󠁵󠁳󠁣󠁡󠁿 ⌚UTC-8 from comment #0)

I have a Firefox session with quite a few pinned tabs. 5 of them (currently; has been 6 at some points in the past few months) are Slack instances.

When I restart, occasionally the Slack tabs are restored as a blank tab -- just completely blank contents, blank URL bar, but the correct Slack icon in the URL bar. The back/forward history still works, so the best way to get back to Slack is to hit back or forward -- and then things are normal. (If I hit forward, back will then keep me in a working state with a good URL in the URL bar.)

(In reply to Alphan Chen [:alchen] from comment #3)

I recall a similar bug before.]

But the URL bar is not blank from previous bug.
:dbaron, could you have a printscreen and browser console log for investigation when you reproduce the problem next time?
One more thing, do you enable fission at that time?

Flags: needinfo?(dbaron)

I often see this in Matrix (chat.mozilla.org) and Gmail pinned tabs. No addons, no fission.

(In reply to Gabriela [:gaby2300] from comment #5)

I often see this in Matrix (chat.mozilla.org) and Gmail pinned tabs. No addons, no fission.

Is the symptom the same as bug 1548508?
Could you have a printscreen and browser console log for investigation?

Flags: needinfo?(gmontagu)

(In reply to David Baron :dbaron: 🏴󠁵󠁳󠁣󠁡󠁿 ⌚UTC-8 from comment #0)

I run nightly, so generally restart twice a day. I think I've been seeing this a few times a week, though I think the frequency has varied a bit since I started seeing it. I believe the first time I saw it was the evening of January 16, the second time was the morning of February 6th, and it's been a little more frequent but on-and-off since then. It tends to happen either to all 5 Slack tabs at once, or to none of them.

(In reply to Mike de Boer [:mikedeboer] from comment #2)

So these kind of bugs are nigh impossible to reproduce and/ or track. The only thing that recently changed that could have an impact as described here is bug 1507287.

Just make the timeline clear. bug 1507287 lands on Mar 19.
The reporter met the problem from January.
I won't combine them into one thing.
But it is welcome if we have log to check or STR to reproduce. :)

Will do as soon as I see the issue.

Flags: needinfo?(gmontagu)

(In reply to Alphan Chen [:alchen] from comment #6)

(In reply to Gabriela [:gaby2300] from comment #5)

I often see this in Matrix (chat.mozilla.org) and Gmail pinned tabs. No addons, no fission.

Is the symptom the same as bug 1548508?
Could you have a printscreen and browser console log for investigation?

Console log Riot site:
to initialise bundle.js:2:754525
Switching to room alias #l10n-community:mozilla.org at event undefined bundle.js:2:754525
StorageManager: Persistent? true bundle.js:2:754525
Switching to room alias #l10n-community:mozilla.org at event undefined bundle.js:2:754525
Homeserver has no integration managers 2 bundle.js:2:754525
El recurso de “https://chat.mozilla.org/bundles/952685db4d8e01c64e64/indexeddb-worker.js” se bloqueó debido a la falta de coincidencia del tipo MIME (“text/html”) (X-Content-Type-Options: nosniff).

Several Gmail accounts tabs:
Nothing on the console.

Attached image Bug1.png —

From the log you passed, it looks like the Riot site encounters some problems of indexedbd.
It may be the problem of why we cannot restore successfully.

El recurso de “https://chat.mozilla.org/bundles/952685db4d8e01c64e64/indexeddb-worker.js” se bloqueó debido a la falta de coincidencia del tipo MIME (“text/html”) (X-Content-Type-Options: nosniff).

Resource "https://chat.mozilla.org/bundles/952685db4d8e01c64e64/indexeddb-worker.js" crashed due to mismatch of MIME type ("text / html") (X-Content-Type-Options : nosniff).

If so, is there some way to fix the issue?

For the logs of comment 9, we may need help from the people who are in charge of "https://chat.mozilla.org/".

(In reply to Alphan Chen [:alchen] from comment #13)

For the logs of comment 9, we may need help from the people who are in charge of "https://chat.mozilla.org/".

Have you asked them for help already?

(In reply to Gabriela [:gaby2300] from comment #14)

(In reply to Alphan Chen [:alchen] from comment #13)

For the logs of comment 9, we may need help from the people who are in charge of "https://chat.mozilla.org/".

Have you asked them for help already?

I paste the log into #synchronicity:mozilla.org.
https://matrix.to/#/!pcfWjiETvnVuspPLPl:mozilla.org?via=mozilla.org&via=matrix.org&via=feneas.org

Did someone reply?

(In reply to Gabriela [:gaby2300] from comment #16)

Did someone reply?

They suggest that you just refresh it at that time. Does refresh work for you?
The reason for this error is "you're trying to restore an old version of the app which has apparently already been removed from production".

Log the replies here.
(Matthew)
Doesn't sound good, but i'm not confident i'm correctly translating the spanish
but if the indexeddb worker doesn't load, then bad times
that URL is 404ing for me, too: https://chat.mozilla.org/bundles/952685db4d8e01c64e64/indexeddb-worker.js

Michael (t3chguy)
the bundle hash on chat.mo is 9f769ac7a648e2ec9507

tulir
https://chat.mozilla.org/bundles/952685db4d8e01c64e64/indexeddb-worker.js returns a 404, but me opening chat.mozilla.org seems to load https://chat.mozilla.org/bundles/9f769ac7a648e2ec9507/indexeddb-worker.js

Matthew
i would recommend hitting refresh

Matthew
you're trying to restore an old version of the app which has apparently already been removed from production

(In reply to Alphan Chen [:alchen] from comment #17)

(In reply to Gabriela [:gaby2300] from comment #16)

Did someone reply?

They suggest that you just refresh it at that time. Does refresh work for you?
No, it does not.

The reason for this error is "you're trying to restore an old version of the app which has apparently already been removed from production".
I am sorry but I don't understand what they are talking about! What old version of the app? What app are they talking about?? It's no app at all! It's just a pinned Firefox tab, either the newly updated Nightly or the recent Release.

Log the replies here.
(Matthew)
Doesn't sound good, but i'm not confident i'm correctly translating the spanish
but if the indexeddb worker doesn't load, then bad times
that URL is 404ing for me, too: https://chat.mozilla.org/bundles/952685db4d8e01c64e64/indexeddb-worker.js

Michael (t3chguy)
the bundle hash on chat.mo is 9f769ac7a648e2ec9507

tulir
https://chat.mozilla.org/bundles/952685db4d8e01c64e64/indexeddb-worker.js returns a 404, but me opening chat.mozilla.org seems to load https://chat.mozilla.org/bundles/9f769ac7a648e2ec9507/indexeddb-worker.js

Matthew
i would recommend hitting refresh

Matthew
you're trying to restore an old version of the app which has apparently already been removed from production

I think they are trying to explain the logs.
The "indexeddb-worker.js" version from the log is not what they use right now.
(old version)
https://chat.mozilla.org/bundles/952685db4d8e01c64e64/indexeddb-worker.js
(current version)
https://chat.mozilla.org/bundles/952685db4d8e01c64e64/indexeddb-worker.js

Since those logs are from "https://chat.mozilla.org/", I can't provide more information or ideas.
Instead, people in the room( #synchronicity:mozilla.org) should be able to discuss the problem you meet. :)

(In reply to Alphan Chen [:alchen] from comment #19)

I think they are trying to explain the logs.
The "indexeddb-worker.js" version from the log is not what they use right now.
(old version)
https://chat.mozilla.org/bundles/952685db4d8e01c64e64/indexeddb-worker.js
(current version)
https://chat.mozilla.org/bundles/952685db4d8e01c64e64/indexeddb-worker.js

Since those logs are from "https://chat.mozilla.org/", I can't provide more information or ideas.
Instead, people in the room( #synchronicity:mozilla.org) should be able to discuss the problem you meet. :)

I am sorry but I don't understand the difference between old and current "indexeddb-worker.js" version.
You are saying that my old version is: https://chat.mozilla.org/bundles/952685db4d8e01c64e64/indexeddb-worker.js and the current one is https://chat.mozilla.org/bundles/952685db4d8e01c64e64/indexeddb-worker.js
Again, I am sorry but both look exactly the same to me.

(In reply to Gabriela [:gaby2300] from comment #20)

(In reply to Alphan Chen [:alchen] from comment #19)

I think they are trying to explain the logs.
The "indexeddb-worker.js" version from the log is not what they use right now.
(old version)
https://chat.mozilla.org/bundles/952685db4d8e01c64e64/indexeddb-worker.js
(current version)
https://chat.mozilla.org/bundles/952685db4d8e01c64e64/indexeddb-worker.js

Since those logs are from "https://chat.mozilla.org/", I can't provide more information or ideas.
Instead, people in the room( #synchronicity:mozilla.org) should be able to discuss the problem you meet. :)

I am sorry but I don't understand the difference between old and current "indexeddb-worker.js" version.
You are saying that my old version is: https://chat.mozilla.org/bundles/952685db4d8e01c64e64/indexeddb-worker.js and the current one is https://chat.mozilla.org/bundles/952685db4d8e01c64e64/indexeddb-worker.js
Again, I am sorry but both look exactly the same to me.

Sorry, I pasted the wrong link.
Current version is https://chat.mozilla.org/bundles/9f769ac7a648e2ec9507/indexeddb-worker.js

Sorry, I pasted the wrong link.
Current version is https://chat.mozilla.org/bundles/9f769ac7a648e2ec9507/indexeddb-worker.js

Sure, no problem!
Could you please tell me how I proceed to get/use the current one then?

I hit the bug with Slack again this morning, although this time with only 2 of the five Slack tabs. There aren't any warnings or errors of interest in the browser console, just:

11:37:11.333 Content Security Policy: Ignoring “'unsafe-inline'” within script-src or style-src: nonce-source or hash-source specified
11:38:10.721
Key key_application of menuitem Application could not be found menu.js:292
    accelText chrome://global/content/elements/menu.js:292
    _computeAccelTextFromKeyIfNeeded chrome://global/content/elements/menu.js:299
    render chrome://global/content/elements/menu.js:326
    connectedCallback chrome://global/content/elements/menu.js:342
    addAllToolsToMenu resource://devtools/client/framework/browser-menus.js:220
    addMenus resource://devtools/client/framework/browser-menus.js:303
    _registerBrowserWindow resource://devtools/client/framework/devtools-browser.js:464
    <anonymous> resource://devtools/client/framework/devtools-browser.js:816
    load resource://devtools/shared/base-loader.js:160
    _require resource://devtools/shared/base-loader.js:346
    requireHook resource://devtools/shared/Loader.jsm:103
    require resource://devtools/shared/base-loader.js:300
    initDevTools resource:///modules/DevToolsStartup.jsm:934
    onPopupShowing resource:///modules/DevToolsStartup.jsm:700
    (Async: EventListener.handleEvent)
    hookWebDeveloperMenu resource:///modules/DevToolsStartup.jsm:702
    hookWindow resource:///modules/DevToolsStartup.jsm:517
    onWindowReady resource:///modules/DevToolsStartup.jsm:462
    onWindowReady self-hosted:844
    _delayedStartup chrome://browser/content/browser.js:2117
    _delayedStartup self-hosted:844
    (Async: EventListener.handleEvent)
    onLoad chrome://browser/content/browser.js:1915
    onLoad self-hosted:844
    (Async: EventHandlerNonNull)
    <anonymous> chrome://browser/content/browser.xhtml:123
Flags: needinfo?(dbaron)

(note that the back button had history in it, and worked to make the tab work correctly)

Actually, it was all 5 slack tabs -- I initially checked while the last 3 of them were still loading, and they had URLs in the URL bar.

So they were initially (while trying to load) in a state where they had a URL in the URL bar, but then they failed to load and got into the weird state.

(In reply to Gabriela [:gaby2300] from comment #22)

Sure, no problem!
Could you please tell me how I proceed to get/use the current one then?

No idea. We need the other's advice.
In your case, you cannot recover the tab after trying to refresh it.
I don't have any idea to fix the problem you meet.
If there are logs after refreshing, could we discuss the logs in the riot room(#Synchronicity)?

I just saw that there is a new version of riot and I tried to close and restore the tab.
In the beginning, I also see a blank page. But it can be recovered when hitting refresh.

I am not seeing the bug anymore, maybe the new version you mention or the Nightly updates.
Should I see it again, I will comment again here.

BTW, Riot is an app, Nightly's chat.mozilla.org pinned tab is a browser's tab. So, what does a new Riot version have to do with Nightly's chat.mozilla.org pinned tab? I would greatly appreciate an explanation!

Hi Gabriela,

Thanks for confirming this issue has been solved on your end.

I’ll mark this ticket as resolved. Please feel free to reopen this bug if you have any troubles.

Regards, Clara

Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(dbaron)
Resolution: --- → WORKSFORME

I've seen this on nightly within the past week or so.

Status: RESOLVED → REOPENED
Flags: needinfo?(dbaron)
Resolution: WORKSFORME → ---

Just saw it again in the nightly upgrade that came out about 3 hours ago (built from 9f3fcb6752b4).

And to me in the same update: 2 of my Gmail pinned tabs blank, Slack pinned tab blank (no URL). Element and Pontoon pinned tabs loaded fine.

See Also: → 1678689

86=affected because I still see this pinned Slack tab problem a few times a week.

status-firefox86: --- → affected

I reproduce this bug again without Fission. I didn't see any obvious Slack error messages in the Browser Console, just a ton of Slack Service Worker messages about fetching and caching assets:

Jan-8 09:05:57.202 [SERVICE-WORKER] asset not found in an existing cache bucket https://a.slack-edge.com/bv1-9/gantry-v2-async-workflow-builder-page-workflow-version.4b5b0c6.min.js service-worker.js:1:50854
Jan-8 09:05:57.202 [SERVICE-WORKER] fetching asset https://a.slack-edge.com/bv1-9/gantry-v2-async-workflow-builder-page-workflow-version.4b5b0c6.min.js service-worker.js:1:50854
Jan-8 09:05:57.202 [SERVICE-WORKER] asset not found in an existing cache bucket https://a.slack-edge.com/bv1-9/gantry-v2-async-workflow-builder-page-workflow-version.4b5b0c6.min.js service-worker.js:1:50854
Jan-8 09:05:57.202 [SERVICE-WORKER] fetching asset https://a.slack-edge.com/bv1-9/gantry-v2-async-workflow-builder-page-workflow-version.4b5b0c6.min.js service-worker.js:1:50854
Jan-8 09:05:57.272 [SERVICE-WORKER] asset found in existing cache bucket, adding to new bucket https://a.slack-edge.com/bv1-9/gantry-v2-async-workflow-builder-segment-form-channel_action.fbbac5c.css service-worker.js:1:50854
Jan-8 09:05:57.272 [SERVICE-WORKER] asset found in existing cache bucket, adding to new bucket https://a.slack-edge.com/bv1-9/gantry-v2-async-workflow-builder-segment-form-channel_action.fbbac5c.css service-worker.js:1:50854
Jan-8 09:05:57.313 [SERVICE-WORKER] asset found in existing cache bucket, adding to new bucket https://a.slack-edge.com/bv1-9/gantry-v2-async-workflow-builder-segment-form-channel_action.634901e.min.js service-worker.js:1:50854
Jan-8 09:05:57.313 [SERVICE-WORKER] asset found in existing cache bucket, adding to new bucket https://a.slack-edge.com/bv1-9/gantry-v2-async-workflow-builder-segment-form-channel_action.634901e.min.js service-worker.js:1:50854
Jan-8 09:05:57.382 [SERVICE-WORKER] asset found in existing cache bucket, adding to new bucket https://a.slack-edge.com/bv1-9/gantry-v2-async-workflow-builder-segment-form-dialog.29482ac.css service-worker.js:1:50854
Whiteboard: [fission-]

Is this the same as bug 1668743?

I have a pinned Slack tab (in a container tab) that failed to restore. Navigating to it doesn't work at all. The only thing that unbroke the functionality was to unregister the Service Worker via about:serviceworkers. I didn't save the URL, but it was a URL containing cold_boot=1.

  • This issue is not limited to the initial restore, navigating back in the history or even directly loading from the location bar doesn't work.
  • Loading any other URL works (e.g. about:addons, another website, about:blank/ (yep, that's an invalid URL)
  • Opening a new tab in a different container, then navigating to Slack works.
  • The problem is consistently reproducible, even across multiple browser restarts.
  • I observed the issue when I started Firefox (after upgrading from 84.0.1 to 84.0.2).
  • When I open the devtools for a website, and use the location bar to navigate to Slack, then the Network tab shows that the request is allegedly canceled with NS_ERROR_DOM_ABORT_ERR
  • The "Network" row of the Gecko Profiler shows that the request is still at the status "Waiting for response"

Interestingly, I do currently not see a new service worker registration. I have NoScript (latest version 11.1.9) that accepts slack.com and slack-edge.com but not slackb.com - I didn't check if it makes a difference.

Attached file broken.moz_log —

Log created as follows:

  1. Start Firefox with MOZ_LOG_FILE=/tmp/broken MOZ_LOG=timestamp,sync,nsHttp:5,DocumentChannel:5 firefox
  2. Focus the location bar of the affected Slack container tab (at about:blank/).
  3. Prepare to capture the relevant logs: 
    mkdir before after
sleep 5; cp -ra broken.* before/ ; echo Ready; sleep 3 ; cp -ra broken.* after/
  4. Quickly get back to Firefox, prepare a app.slack.com URL, wait until "Ready" appears in the console and then press Enter to try and navigate to it.
  5. After 3 seconds, get the difference diff -r before/ after/ and extract the relevant parts out of it. I have removed > and replaced cookies with REDACTED, but other than that the log has not been changed. Across all attempts, the result was quite consistent - broken.moz_log contained all relevant entries.

Inspired by :asuth's comment in a similar bug (bug 1678795) at https://bugzilla.mozilla.org/show_bug.cgi?id=1678795#c40 , I visited about:preferences to look at the size of the data of Slack (at the "Manage Cookies and Site Data" section). It's 2.1GB. I use Slack in one container, but I have accidentally opened it in a different container before, so it may be possible that the affected container (that hosts my pinned tab) uses less than 2.1 GB.

See Also: → 1678795
status-firefox87: --- → affected
Summary: pinned slack tabs sometimes don't restore correctly → pinned Slack tabs sometimes don't restore correctly

(In reply to Rob Wu [:robwu] from comment #38)

size of the data of Slack (at the "Manage Cookies and Site Data" section). It's 2.1GB. I use Slack in one container,

I have the same slack won't restore issue (win10), my app.slack.com storage is 750MB.

Does it only happen for pinned tabs, or is the issue also visible when you restart Firefox with Slack as normal tab and selected when triggering the restart? I read through the comments but wasn't able to find an answer for that yet.

I ran into this for the first time this week, for Slack but also for Linear (linear.app). It has happened to me quite a few times since then, but not always (when I just quit Nightly and started it again, the pinned tabs loaded as normal).

Not a Fission bug

Whiteboard: [fission-] → [not-a-fission-bug]

I also have Slack in an app tab, and it's frequently blank after session restore. But if I use the URL bar in that tab to navigate to Slack manually, it loads as expected. app.slack.com is taking up 1.3GB for me.

I reproduce this bug at least once a day. (I restart Nightly a couple times a day.) I've also reproduced this bug twice in a non-pinned tab that was session restored (because it was the focused non-pinned tab in a foreground window).

Is there any debug info or logging I can capture to help debug this? Do we know whether this bug also happens in Firefox Beta and Release or just Nightly?

Looks like :asuth is fixing a ServiceWorker issue in bug 1668743 comment 25 that may be related.

Like others reported, app.slack.com is using a lot of storage in my browser: 1.1 GB. Does Slack use this much storage in Chrome?

(In reply to Henrik Skupin (:whimboo) [⌚️UTC+1] from comment #40)

Does it only happen for pinned tabs, or is the issue also visible when you restart Firefox with Slack as normal tab and selected when triggering the restart? I read through the comments but wasn't able to find an answer for that yet.

I got a user report who experienced this issue:

  • 469MB in Storage (so different from bug 1678795 mentioned in comment 38)
  • Opening Slack in a new window/(non-pinned) tab doesn't resolve the issue. Slack doesn't load in a new window.
  • After restarting Firefox, the pinned tab is not restored (I guess because Slack wasn't loaded at the time of exiting Firefox), but after navigating back in the pinned tab (to Slack) or opening Slack in a new window, Slack loads normally.

Like the others, I've been encountering what looks like the same issue for a while now (possibly a year or more?), and it just happened again on Firefox Developer Edition 90b3 / Gnome 40 on Xorg.

(I believe this matches with the symptoms above: I have a pinned Slack tab in a "Personnal" container, that sometimes — around once every 1-2 weeks, but this is not a very active Slack workspace — goes entirely blank and cannot be fixed by opening a new tab or restarting Firefox. The only thing that fixes it is removing all Slack data from the "Manage Data" dialog in the Firefox preferences (not cookies, just local storage). The data used by app.slack.com is often fairly large, around a few 100s MB.)

I have a Nightly profile where this is consistently happening. My profile is now in a state where I cannot open Slack anymore. Not after a restart, not in a new window. It does however work in a private mode window.

I can't share my whole profile but if anyone wants to debug this with me, please let me know. I made a copy of the profile to keep it around in this state. Ping me on Slack please.

You are likely hitting bug 1678795 - see bug 1678795 how to resolve the issue temporarily.

This just happened to me on 90b6. I used the same workaround - go into about:serviceworkers and Unregister Slack.

I pinged some Slack folks about this bug. Waiting for their response...

See Also: → 1237041, 1321406, 1668668
Summary: pinned Slack tabs sometimes don't restore correctly → pinned Slack tabs sometimes don't restore correctly on startup
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: