Opened 4 years ago

Closed 4 years ago

#16692 closed defect (duplicate)

New twitter feature makes Tor Browser crash

Reported by: mrphs Owned by: tbb-team
Priority: Very High Milestone:
Component: Applications/Tor Browser Version:
Severity: Keywords:
Cc: brade, mcs Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by mrphs)

There's this new feature in twitter that if you move your mouse over an avatar, it tries to show you a preview of their profile. And it makes Tor Browser to crash.

I managed to reproduce it a bunch of times on OS X with TB 5.0a3.

Child Tickets

Change History (7)

comment:1 Changed 4 years ago by mrphs

Description: modified (diff)

comment:2 Changed 4 years ago by gk

Priority: majorcritical
Status: newneeds_information

Is that with a default Tor Browser? Or do you use the security level "High"? I suspect you are running into a form of #16495 which should be fixed in the upcoming 5.0a4.

Last edited 4 years ago by gk (previous) (diff)

comment:3 Changed 4 years ago by mcs

Cc: brade mcs added

Yes, please let us know what non-default settings you are using, if any. I was unable to get the "on hover" profile preview feature to work at all in TB 5.0a3. In TB 4.5.3 it worked OK for me on all security slider settings below "High" and did not crash even when I manually set svg.in-content.enabled = false.

comment:4 Changed 4 years ago by mcs

For reference, here is a tweet that explains this new Twitter feature:
https://twitter.com/twitter/status/626503872186482688

comment:5 Changed 4 years ago by mrphs

I, indeed had my security slider set to "High-Security". I'd sign on twitter, and then enable JS, hover on someone's avatar and it crashes.

Last edited 4 years ago by mrphs (previous) (diff)

comment:6 Changed 4 years ago by mrphs

A quick workaround is to bring security slider down to 'medium-high'. so far I haven't observed any crashes.

comment:7 Changed 4 years ago by gk

Resolution: duplicate
Status: needs_informationclosed

IIRC this was fixed for you in 5.0a4. Thus, resolving this as a duplicate of #16495.

Note: See TracTickets for help on using tickets.