Marco Castelluccio [:marco] Reporter
	Description • 9 years ago

I often need to kill the script running in a Travis page to get the browser responsive again.

	Justin [:JW_SoftvisionQA]
	Comment 1 • 9 years ago

Could you please provide more information on this bug? Ie. Steps, Screenshots, expected and actual resuts, etc.

	Marco Castelluccio [:marco] Reporter
	Comment 2 • 9 years ago

To reproduce, simply open a Travis build results page (e.g. https://travis-ci.org/mozilla/pluotsorbet/builds/68736884) and do something (e.g. scroll).
It should be fast, but it's pretty slow.

	Liviu Cirdei
	Comment 3 • 8 years ago

User Agent 	Mozilla/5.0 (X11; Linux x86_64; rv:47.0) Gecko/20100101 Firefox/47.0
Build ID 	20160127030236

Reproduced this on Firefox 44 and Nightly 47.

	Kosta H
	Comment 4 • 8 years ago

I experience the same issue. I'm not sure it's a Linux specific problem; a friend using a Mac has the same issue.

	Dennis Schubert [:denschub]
	Comment 5 • 7 years ago

Adding the quantum flow label, the build overview is still slow in Firefox, and there are other application affected by something similar as well (see 'see also').

	:Harald Kirschner :digitarald
	Comment 6 • 7 years ago

Could you please add a performance profile for investigating the issue?

	Dennis Schubert [:denschub]
	Comment 7 • 7 years ago

After I did not have any luck reproducing any performance issues on my MacBook, I did intensive testing on the Quantum Reference Device.

Using 56 and 55, I have a fair bit of jank during scrolling. However, when using 57 Beta, everything is really smooth, even on long travis build result pages. I clicked around a bit to see all UI part, but could not make out any specific thing that's slow enough to cause any notable hang.

I could do a bisect and see when we ixed it, but I consider that as a win out of general Quantum performance work, which is awesome. Because of that, I'll close this as fixed. If anyone feels like we should have more information about what caused jank in the past, I can do some profiling and analysis on old versions, but I don't think that's very useful.

Also, if someone still has performance issues with 57, we can reopen. :)