LinkedIn page freezes Tor Browser

The following page freezes with Tor Browser Bundle 3.5 on Linux:

http://no.linkedin.com/pub/torfinn-ingolfsen/3/6a9/981

It does not freeze for vanilla Firefox 24 ESR. Occurs on two different Linux machines (one 32-bit, one 64-bit).

Aside: There seems to be no Trac milestone, version, or component applicable to TBB. Am I reporting to the correct tracker?

Trac:
Username: bernie.allen

added component::applications/tor browser priority::medium reporter::bernie.allen resolution::worksforme severity::normal status::closed tbb-crash tbb-firefox-patch tbb-usability-website type::defect labels

Reproduced on Windows, therefore not Linux specific.

Trac:
Username: bernie.allen
Summary: LinkedIn page freezes Tor Browser on Linux to LinkedIn page freezes Tor Browser

#9901 (closed)

Trac:
Component: - Select a component to TorBrowserButton
Status: new to closed
Resolution: N/A to duplicate

I just reproduced this on TBB 3.6.2.

See also https://blog.torproject.org/blog/tor-browser-362-released#comment-63529

Should we reopen, or is it a new issue?

Trac:
Cc: N/A to gk, mikeperry

Replying to arma:

I just reproduced this on TBB 3.6.2.

How?

Trac:
Resolution: duplicate to N/A
Status: closed to reopened

On my linux 64-bit tbb 3.6.2, which had some other tabs open and had been in use for a while, I went to the address bar and typed in "linkedin.com" and hit enter.

Soon after, my browser window didn't respond anymore.

I just did it again, same result.

I just tried it on a freshly started linux 64-bit TBB 3.6.2, and the page loaded, but it used a lot of cpu, and after maybe 5 or 10 seconds tor browser is now at 100% cpu and the window won't respond.

Confirmed on Linux, I went to linkedin.com without logging in, switched to check irc for a minute then went back to TB to find it all frozen.

Replying to Sherief:

Confirmed on Linux, I went to linkedin.com without logging in, switched to check irc for a minute then went back to TB to find it all frozen.

Same thing for Windows.

Trac:
Cc: gk, mikeperry to gk, mikeperry, Sherief

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

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

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

Trac:
Component: TorBrowserButton to Firefox Patch Issues

I was able to reproduce this with stock 3.6.2, 32-bit, under Debian 7. Page briefly froze, then unfroze, then entire browser froze. Quite strange.

Also confirmed on tor-browser-linux64-3.6.1_en-US. Let me know if any particular details to be obtained during a hang would be useful.

Note that I don't get a crash unless I let the hang continue un-interrupted for a period of some many seconds. Early on in hang behavior you can close the offending tab and recover browser usable state.

Trac:
Username: anon

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

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

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

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

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

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

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

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

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

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

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

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

Look at this https://bugzilla.mozilla.org/show_bug.cgi?id=763227 They says it's site problem not browser!

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

Trac:
Resolution: N/A to fixed
Status: reopened to closed

Trac:
Priority: normal to blocker
Type: defect to task
Component: Firefox Patch Issues to Ponies
Summary: LinkedIn page freezes Tor Browser to Fill the web with tadaboom

Reverted ticket change made by cypherpunks.

Complaint filed with LinkedIn regarding this bug.

Trac:
Priority: blocker to normal
Summary: Fill the web with tadaboom to LinkedIn page freezes Tor Browser
Type: task to defect
Component: Ponies to Firefox Patch Issues

Trac:
boom.zip

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

Trac:
tadaboom.html

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

Trac:
test.html

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

Trac:
triggers_bug.txt

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

Trac:
Status: closed to reopened
Resolution: fixed to N/A

Trac:
Keywords: N/A deleted, tbb-usability-website added

Trac:
Component: Firefox Patch Issues to Tor Browser
Keywords: N/A deleted, tbb-firefox-patch added

#12755 (moved) is a duplicate of this one.

Still an issue on Tor Browser 4.0 (Linux 32-bit).

Trac:
Keywords: N/A deleted, tbb-crash added
Sponsor: N/A to N/A
Severity: N/A to Normal

Above link gives me an authwall, please reopen if you can reproduce it.

Trac:
Status: reopened to closed
Resolution: N/A to fixed
Reviewer: N/A to N/A

Correct resolution

Trac:
Status: closed to reopened
Resolution: fixed to N/A

Trac:
Status: reopened to closed
Resolution: N/A to worksforme

I was told that this bug reappeared in firefox and is not reproducible with current Tor Browser.

login issue, iff "dom.enable_performance" == false also noticed an additional 'sensitivity' to that param, but with Instagram: https://www.reddit.com/r/firefox/comments/9oibv2/since_today_domenable_performance_false_causes/ users were NOT having LinkedIn login problems as recently as 2-3 weeks ago Checking with latest Tor, verified in about:config "dom.enable_performance;false" => NO problem logging in. Same setting in FF/release, login FAILs. Does setting that param in user.js break anything else? It was mentioned in #firefox that it might have to do with LinkedIn tracking.