News for hackers. Stuff that matters.
Re:Firefox 61.0 Released by bzbarsky on Tuesday June 26, 2018 @12:45PM (#17402130)
Would it be possible to get access to the page in question to try to diagnose this problem?

If it would, please let me know at bzbarsky at mit dot edu.

If not, would you be willing to use a Firefox nightly and follow the steps at https://developer.mozilla.org/en-US/docs/Mozilla/Performance... then send me a link to the profile that gets generated?

Re:Firefox 61.0 Released by matthew-wegner on Tuesday June 26, 2018 @02:18PM (#17402869)
Re:Firefox 61.0 Released by bzbarsky on Tuesday June 26, 2018 @02:37PM (#17403004)
Thank you! I'll give that a shot.
Re:Firefox 61.0 Released by xoa on Tuesday June 26, 2018 @01:34PM (#17402552)
I’ll try to repro myself first, already started up a test both on metal and a VM on a few systems. If it’s dealt with probably not much point investigating further. Should know within a day or two (or sooner, maybe it’s even regressed a bit). I’ll try to do a proper performance profile a report after that as well as ping a contact at Ubiquiti. They’d be the best placed to really dig into it.
Re:Firefox 61.0 Released by bzbarsky on Tuesday June 26, 2018 @02:38PM (#17403008)
Thank you! Please let me know how things look.

I agree that if it's a leak on the Ubiquiti side they would be best placed to deal with that aspect, but there might be things we can do better on the Firefox side to handle pages leaking too...