Opened 18 months ago

Closed 7 months ago

#26579 closed defect (wontfix)

about:tor very slow to load

Reported by: arthuredelstein Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: #23073 Points:
Reviewer: Sponsor:

Description

On a slow Linux machine, I notice that about:tor is extremely slow to load. The browser window appears, but the page only appears after 20 or 30 seconds. On a faster machine (multicore) the page appears quickly. This might be related to #26381, but I think it's more likely a separate issue.

Child Tickets

Change History (7)

comment:1 Changed 17 months ago by cypherpunks

It's with New Identity where it's most noticeable in most cases.

comment:2 Changed 17 months ago by cypherpunks

Ugh, it seems to be due to the same NoScript problem that I encountered sometimes when opening links in new tabs (see #23719#comment:9), here's the console thing:

[NoScript] Cannot collect noscript activity data Error: Message manager disconnected
Stack trace:
collectSeen@moz-extension://[No🔥Script🔥's UUID]/bg/main.js:265:38
 Message manager disconnected collectSeen@moz-extension://[No🔥Script🔥's UUID]/bg/main.js:265:38
  log.js:12:5
	error moz-extension://[No🔥Script🔥's UUID]/lib/log.js:12:5
	collectSeen moz-extension://[No🔥Script🔥's UUID]/bg/main.js:274:10
Webconsole context has changed
Ignoring response to aborted listener for 4880
NS_ERROR_NOT_AVAILABLE: Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIWebNavigation.loadURIWithOptions]  browser-child.js:359
[NoScript] Cannot collect noscript activity data Error: Could not establish connection. Receiving end does not exist.
Stack trace:
collectSeen@moz-extension://[No🔥Script🔥's UUID]/bg/main.js:265:38
 Could not establish connection. Receiving end does not exist. collectSeen@moz-extension://[No🔥Script🔥's UUID]/bg/main.js:265:38
  log.js:12:5
	error moz-extension://[No🔥Script🔥's UUID]/lib/log.js:12:5
	collectSeen moz-extension://[No🔥Script🔥's UUID]/bg/main.js:274:10
Torbutton WARN: no SOCKS credentials found for current document.

Tested on Linux.

comment:3 Changed 17 months ago by gk

Parent ID: #23073

I actually think that's due to selfrando. Because when new content processes are created the randomization gets launched and it takes while until this is finished. I noticed that in the esr52-based alpha series, too, although I have to agree that it got worse when switching to esr60, probably due to increased binary size.

I could be wrong, though. But let's tag it as a selfrando bug barring further investigation.

comment:4 in reply to:  3 Changed 17 months ago by cypherpunks

Replying to gk:

I actually think that's due to selfrando. Because when new content processes are created the randomization gets launched and it takes while until this is finished.

Looking at about:performance while emulating this behavior (new tab+website => new content process shown there) seems to confirm this.

comment:5 Changed 12 months ago by jb.1234abcd

TB 8.5a6

It times out during "Perform TLS handshake with www.torproject.org" as default homepage.
It works fast with e.g. www.google.com in another tab.

comment:6 Changed 7 months ago by gk

Closed #30306 as duplicate.

Last edited 7 months ago by gk (previous) (diff)

comment:7 Changed 7 months ago by gk

Resolution: wontfix
Status: newclosed

We removed selfrando support in bug 30377, thus this is a WONTFIX.

Note: See TracTickets for help on using tickets.