bugzilla.mozilla.org will be intermittently unavailable on Saturday, March 24th, from 16:00 until 20:00 UTC.
Created attachment 8712958 [details] screenshot of problem Since upgrading to Firefox 44 on Fedora, Google Keep doesn't work. It loads slowly, with one core using ~50%, and as soon as I click on a note, I get a message (attached).
This is not a Firefox regression. The problem is with NoScript 220.127.116.11, even when everything on the keep (and all other google) page is allowed to run scripts. If NoScript is completely disabled or removed, Keep always works fine (CPU hog though). If it's enabled, but allows scripts to run, Keep always fails, with the reload problem. Curiously the identical error message always happens (whether NoScript is enabled or not) with the Google Keep Addon, so it seems fundamentally broken at the moment.
Giorgio, is this something you can look into?
(In reply to :Gijs Kruitbosch from comment #4) > Giorgio, is this something you can look into? I'll do ASAP, thanks for putting me in the loop.
Giorgio, is there any progress on this bug ? I just keep running into this problem on aurora(51) and beta(50) on macOS with super high cpu usage taken from FF. On beta(non-e10s), it even frozen everything so that I need to force quit FF to restart. With e10s, basically all other tabs page are frozen too and hardly to do anything.
Priority: -- → P3
I'm not using NoScript anymore these days, just Privacy Badger and uBlock and with those the problem doesn't happen.
It appears to me a content related issue so that I can just reproduce the problem on my work account but personal account. It's reproducible with clean profile either. Could you let me know what kind of info is required for further debugging ? And the instructions to generate them. Thanks.
Mass-closing old Extension Compatibility bugs that relate to legacy add-ons or NPAPI plug-ins. If you think this bug is still valid, please reopen or comment. Sorry for the bug spam, and happy Friday!
Status: NEW → RESOLVED
Last Resolved: 21 days ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.