Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#19362 closed defect (duplicate)

Linux-64 Tor Browser 6.0.1 performance is so terrible it is a security vulnerabality

Reported by: 49ax56xr36 Owned by: tbb-team
Priority: High Milestone:
Component: Applications/Tor Browser Version:
Severity: Major Keywords: tbb-usability, tbb-6.0-issues, tbb-regression
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Linux 64-bit 6.0.1 release performance is so bad it will compel users to stay on 5.5.5.

Unusable on a single core 2.3GHz CPU, 1G free memory, "medium-high" security slider. Just as bad with or without Javascript enabled.

Unacceptable.

Child Tickets

Change History (7)

comment:1 Changed 3 years ago by cypherpunks

Linux user here. For me performance is perfectly fine. There is no noticeable difference between TBB 5.5 and 6.

Bug reporter, filing this is pointless without you providing a lot more details so that your issues can be reproduced.

comment:2 Changed 3 years ago by gk

Resolution: worksforme
Status: newclosed

I've tested this on different Linux systems and don't see any problems.

comment:3 Changed 3 years ago by gk

Maybe that's related to #19276?

comment:4 in reply to:  3 ; Changed 3 years ago by 49ax56xr36

Replying to gk:

Maybe that's related to #19276?

Yes #19276 was the problem. Setting gfx.xrender.enabled = false fixed it.

The regression is so bad that initially I ran 6.0.1 for less than 20 minutes and decided not to dig into it because it implied QC disaster. Was not obvious that scrolling is the performance fail.

Should have been mentioned up-front in the released announcement.

comment:5 in reply to:  4 ; Changed 3 years ago by gk

Keywords: tbb-usability tbb-6.0-issues tbb-regression added
Resolution: worksforme
Status: closedreopened

Replying to 49ax56xr36:

Replying to gk:

Maybe that's related to #19276?

Yes #19276 was the problem. Setting gfx.xrender.enabled = false fixed it.

The regression is so bad that initially I ran 6.0.1 for less than 20 minutes and decided not to dig into it because it implied QC disaster. Was not obvious that scrolling is the performance fail.

Should have been mentioned up-front in the released announcement.

We would have done that had we known about this problem. I updated the blog post now. Duplicating this in favor of #19276 where the discussion is happening.

comment:6 Changed 3 years ago by gk

Resolution: duplicate
Status: reopenedclosed

comment:7 in reply to:  5 Changed 3 years ago by cypherpunks

Replying to gk:

Replying to 49ax56xr36:

Replying to gk:

Maybe that's related to #19276?

Yes #19276 was the problem. Setting gfx.xrender.enabled = false fixed it.

The regression is so bad that initially I ran 6.0.1 for less than 20 minutes and decided not to dig into it because it implied QC disaster. Was not obvious that scrolling is the performance fail.

Should have been mentioned up-front in the released announcement.

We would have done that had we known about this problem. I updated the blog post now. Duplicating this in favor of #19276 where the discussion is happening.

The link in the blog post to the ticket does not work because it has no href attribute.

Note: See TracTickets for help on using tickets.