Bug #11507

Watching WebM videos in the Tor Browser is broken on single core systems

Added by anonym 2016-06-04 11:08:05 . Updated 2016-09-16 07:19:52 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_2.6
Start date:
2016-06-04
Due date:
% Done:

100%

Feature Branch:
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Browser
Deliverable for:

Description

The is a regression introduced with Tor Browser 6.0 in Tails 2.4~rc1. Possibly it is an upstream Firefox bug, introduced in the Tor Browser when it was rebased on the 45esr branch.

Subtasks

History

#1 Updated by anonym 2016-06-04 11:21:24

I’ve verified that tor-browser-linux64-6.0_en-US.tar.xz is affected by the same issue in a single core Debian Jessie VM. We need to check in vanilla Firefox 45 too.

#2 Updated by anonym 2016-06-04 11:38:43

I have disabled the “Watching a WebM video” Tor Browser test in commit:08c08e67937f3d6fadd266dc2ab43c0877b2963e.

#3 Updated by anonym 2016-06-04 12:21:07

> We need to check in vanilla Firefox 45 too.

Reproduced in a single-core Debian Sid VM with Firefox 45.1.1esr. I’ll report this upstream.

#4 Updated by anonym 2016-06-04 12:37:41

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 20
  • Type of work changed from Research to Wait

anonym wrote:
> I’ll report this upstream.

Done: https://bugzilla.mozilla.org/show_bug.cgi?id=1278051

#5 Updated by intrigeri 2016-06-06 02:46:47

FTR I have some concerns with fully deleting the test without having this change reverted somewhere else (e.g. on the branch for Feature #6729 perhaps?): it seems to me that it creates a risk for us to never reintroduce it.

#6 Updated by anonym 2016-06-06 04:38:59

intrigeri wrote:
> FTR I have some concerns with fully deleting the test without having this change reverted somewhere else (e.g. on the branch for Feature #6729 perhaps?): it seems to me that it creates a risk for us to never reintroduce it.

Yes, my bad. Fixed in commit:11a7a9a421933048d0fd6b246e9941739df6091d in the test/10971-more-CPUs-for-TailsToaster branch.

#7 Updated by anonym 2016-06-08 01:35:04

  • Target version changed from Tails_2.4 to Tails_2.5

#8 Updated by intrigeri 2016-07-13 12:32:57

  • Target version changed from Tails_2.5 to Tails_2.6
  • Type of work changed from Wait to Communicate

I’ve answered the question that upstream asked. Let’s call this a communication task rather than a mere waiting one. Still, worth postponing.

#9 Updated by intrigeri 2016-08-31 04:53:39

  • Type of work changed from Communicate to End-user documentation

We did what we could upstream, and they closed the bug report. On our side, our test suite is not affected anymore, and I guess that very few actual users can be affected since almost all CPUs on systems that can run Tails these days have >1 hyperthread. So I think that we should simply document this on our known issues page and then close this ticket.

#10 Updated by anonym 2016-09-16 07:19:52

  • Status changed from In Progress to Resolved
  • Assignee deleted (anonym)
  • % Done changed from 20 to 100

intrigeri wrote:
> So I think that we should simply document this on our known issues page and then close this ticket.

Done in commit:c717c8e02aed6f7c747794e19c3dfa08825eacd6.