Closed Bug 1698745 Opened 4 years ago Closed 4 years ago

unable to open https://friendsofredaxo.slack.com/ - Error when attaching target

Categories

(Core :: Networking: HTTP, defect)

Firefox 88
defect

Tracking

()

RESOLVED DUPLICATE of bug 1678795

People

(Reporter: maggus.staab, Unassigned)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:88.0) Gecko/20100101 Firefox/88.0

Steps to reproduce:

Actual results:

no navigation happens. the browser just stays at the empty new tab.

error in the browser console is

Error when attaching target: Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIWorkerDebugger.initialize]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: resource://devtools/server/connectors/worker-connector.js :: connectToWorker/< :: line 36" data: no] from: server1.conn0.contentProcess17848/workerDescriptor12
onPacket resource://devtools/shared/protocol/Front.js:361
DevTools RDP*request resource://devtools/shared/protocol/Front.js:288
name resource://devtools/shared/protocol/Front/FrontClassWithSpec.js:46
_attach resource://devtools/client/fronts/descriptors/worker.js:92
target-command.js:168:15
_onTargetAvailable resource://devtools/shared/commands/target/target-command.js:168

this website worked like any other a few weeks ago

Expected results:

the requested url should be opened, like any other website can be opened with the firefox instance.

I can reproduce the error only on https://friendsofredaxo.slack.com/ atm

as a side note:

I should have a already established session with https://friendsofredaxo.slack.com/ which the browser is not able to continue. I guess deleting my site data for this url will make it work again. I didn't do this right now, because I want be able to reproduce this issue for further debugging

Hey maggus,
I tried reproducing this issue on the latest versions of Firefox Nightly 88.0a1 (2021-03-17) , beta 87.0 and release 86.0.1 but the connextion goes through for me.

Can you test the issue while in Safe Mode? You can find helpful info here : https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode .
Also a fresh new profile could help. You can find more about creating a new profile here : https://support.mozilla.org/en-US/kb/troubleshoot-and-diagnose-firefox-problems#w_6-create-a-new-firefox-profile .
If possible, you can test this issue on the nightly build as well. Download the build from : https://www.mozilla.org/en-US/firefox/nightly/all/ .

Flags: needinfo?(maggus.staab)

Hey.

Can you test the issue while in Safe Mode?

I can reproduce the same issue in safe-mode. the error I am getting in safe-mode is a bit different though

Error when attaching target: Error: Protocol error (noSuchActor): No such actor for ID: server1.conn0.contentProcess1400/workerDescriptor81/console3 from: server1.conn0.contentProcess1400/workerDescriptor81/console3
    onPacket resource://devtools/shared/protocol/Front.js:361
    DevTools RDP*request resource://devtools/shared/protocol/Front.js:288
    name resource://devtools/shared/protocol/Front/FrontClassWithSpec.js:46
    startListeners resource://devtools/client/fronts/webconsole.js:424
    attachConsole resource://devtools/client/fronts/targets/target-mixin.js:432
target-command.js:168:15
    _onTargetAvailable resource://devtools/shared/commands/target/target-command.js:168

If possible, you can test this issue on the nightly build as well.
I am already on firefox nightly - in fact I initially reported the issue on FF nightly

I can't reproduce the error in a private window (where no existing http session gets resumed)

Flags: needinfo?(maggus.staab)

sorry mixed the quoting in the above comment

If possible, you can test this issue on the nightly build as well.

I am already on firefox nightly - in fact I initially reported the issue on FF nightly

The Bugbug bot thinks this bug should belong to the 'Core::Networking: HTTP' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → Networking: HTTP
Product: Firefox → Core

Thanks for the report.
Could you record a profile using profiler.firefox.com/ ?
Also could you record some HTTP logs and prefferably send them via email? Instructions here

Flags: needinfo?(maggus.staab)

please find the profile starting from typing into the addressbar, until the error happens here https://share.firefox.dev/2QrIicx

Flags: needinfo?(maggus.staab)

attached you can find the http logging

Flags: needinfo?(valentin.gosu)

My best guess is that the channel is cancelled by a service worker.

2021-03-23 14:03:46.034000 UTC - [Parent 19892: Main Thread]: D/nsHttp HttpAsyncAborter::AsyncAbort [this=1e89d1d4000 status=80530014]

NS_ERROR_DOM_ABORT_ERR = 0x80530014,

Andrew, do you have any idea how we'd debug this futher?

Flags: needinfo?(valentin.gosu) → needinfo?(bugmail)

This is unfortunately bug 1678795 which I'm actively working towards a fix on. If you clear the data for the origin and related slack origins, that should workaround the issue. See https://support.mozilla.org/en-US/kb/clear-cookies-and-site-data-firefox#w_clear-cookies-for-any-website and you would want to search on "slack.com" and clear all of the slack origins.

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Flags: needinfo?(bugmail)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: