Search found 13 matches
- Tue Jan 05, 2016 6:50 am
- Forum: NoScript Support
- Topic: Add-on interaction problems: NoScript, KeeFox, and CTR
- Replies: 14
- Views: 11018
Re: Add-on interaction problems: NoScript, KeeFox, and CTR
Thanks for the quick fix! It looks good so far, but I'll let you know if I encounter any issues.
- Sat Jan 02, 2016 1:06 am
- Forum: NoScript Support
- Topic: Add-on interaction problems: NoScript, KeeFox, and CTR
- Replies: 14
- Views: 11018
Re: Add-on interaction problems: NoScript, KeeFox, and CTR
Thanks, and happy new year to you all as well!
- Thu Dec 31, 2015 4:53 am
- Forum: NoScript Support
- Topic: Add-on interaction problems: NoScript, KeeFox, and CTR
- Replies: 14
- Views: 11018
Re: Add-on interaction problems: NoScript, KeeFox, and CTR
I would imagine that the crash signatures for all manually-induced crashes are similar, No they're not. If it worked this way then manually crashing Firefox would be pointless and no one would ask you to do that as part of troubleshooting a hang. Well, I'm not a Firefox developer, so I won't argue ...
- Sat Dec 12, 2015 11:15 pm
- Forum: NoScript Support
- Topic: Add-on interaction problems: NoScript, KeeFox, and CTR
- Replies: 14
- Views: 11018
Re: Add-on interaction problems: NoScript, KeeFox, and CTR
Nvidia driver, so does the issue persist if you disable Hardware Acceleration in FF (& then restart FF)? Any change if you restart your computer in Safe Mode with Networking? Or otherwise disable your A/V (Norton)? Unfortunately, no to all three, the issue is reproducible in each of those cases...
- Sat Dec 12, 2015 4:23 am
- Forum: NoScript Support
- Topic: Add-on interaction problems: NoScript, KeeFox, and CTR
- Replies: 14
- Views: 11018
Re: Add-on interaction problems: NoScript, KeeFox, and CTR
Which part of the report, specifically, makes you think that?
If that's the case, I can open a bug with FF as well, and point to this crash data.
Thanks.
If that's the case, I can open a bug with FF as well, and point to this crash data.
Thanks.
- Fri Dec 11, 2015 11:33 pm
- Forum: NoScript Support
- Topic: Add-on interaction problems: NoScript, KeeFox, and CTR
- Replies: 14
- Views: 11018
Re: Add-on interaction problems: NoScript, KeeFox, and CTR
My apologies for my delay in responding; I was out of town for a while and away from my primary computer. I have not yet been able to replicate the complete hang I was experiencing before, but the proof-of-concept code that I posted still produces the high CPU usage and general slowdown and lag in t...
- Sun Nov 22, 2015 9:16 am
- Forum: NoScript Support
- Topic: Add-on interaction problems: NoScript, KeeFox, and CTR
- Replies: 14
- Views: 11018
Add-on interaction problems: NoScript, KeeFox, and CTR
Hello, I'm having an issue where NoScript, in conjunction with KeeFox and a specific configuration of Classic Theme Restorer (having the address bar on a second toolbar) causes Firefox to have issues when opening pop-up windows with no toolbars. When clicking a link that opens a pop-up, Firefox's CP...
- Sat Jun 29, 2013 10:05 pm
- Forum: NoScript Support
- Topic: [RESOLVED] cloudfront enabled itself temporarily (?)
- Replies: 26
- Views: 13037
Re: cloudfront enabled itself temporarily (?)
I was not able to reproduce this issue by the following steps:
1. New Profile
2. Install NoScript & restart
3. Visit http://www.rocsidiaz.com/
The only javascript that executed was from googleapis.com. facebook.net, brightcove.com, and rocsidiaz.com were all properly blocked.
1. New Profile
2. Install NoScript & restart
3. Visit http://www.rocsidiaz.com/
The only javascript that executed was from googleapis.com. facebook.net, brightcove.com, and rocsidiaz.com were all properly blocked.
- Sat Jun 29, 2013 9:45 pm
- Forum: NoScript Support
- Topic: select Google Apps not working at work, ok at home !?!
- Replies: 3
- Views: 1985
Re: select Google Apps not working at work, ok at home !?!
By Google Calendar, I assume he just means http://calendar.google.com/.
- Sat Jun 29, 2013 1:12 am
- Forum: NoScript Support
- Topic: NS leaks memory like a firehose on specific site
- Replies: 5
- Views: 2706
Re: NS leaks memory like a firehose on specific site
I have narrowed this down to a combination of NS and FoxyProxy Standard 4.2. After researching a bit, it seems that the FP team pulled the 4.2 version, but it was not hard-blocked by Mozilla, so while I auto-updated to 4.2 initially, I was never forced to roll back. Installing FP Standard 4.1.4 (cur...
- Sat Jun 29, 2013 12:00 am
- Forum: NoScript Support
- Topic: NS leaks memory like a firehose on specific site
- Replies: 5
- Views: 2706
Re: NS leaks memory like a firehose on specific site
Some crash reports (ordered newest to oldest):
https://crash-stats.mozilla.com/report/ ... 9ae2130628
https://crash-stats.mozilla.com/report/ ... 0ec2130626
https://crash-stats.mozilla.com/report/ ... 48d2130626
https://crash-stats.mozilla.com/report/ ... 32b2130626
https://crash-stats.mozilla.com/report/ ... 9ae2130628
https://crash-stats.mozilla.com/report/ ... 0ec2130626
https://crash-stats.mozilla.com/report/ ... 48d2130626
https://crash-stats.mozilla.com/report/ ... 32b2130626
- Fri Jun 28, 2013 10:26 pm
- Forum: NoScript Support
- Topic: NS leaks memory like a firehose on specific site
- Replies: 5
- Views: 2706
Re: NS leaks memory like a firehose on specific site
I am not at the machine in question, but I will reply to as many questions as I can at this time. Yes, I only need to open that page, not even allow any domains. This will happen even if it is the first page I open in a session. Once I open the page, there's no stopping the leak; even closing the ta...
- Fri Jun 28, 2013 7:20 am
- Forum: NoScript Support
- Topic: NS leaks memory like a firehose on specific site
- Replies: 5
- Views: 2706
NS leaks memory like a firehose on specific site
When I visit the site http://girlsonfilm.rubberslug.com/ (not categorically NSFW--it's a gallery of old anime cels) NS leaks memory like crazy (~100 MB/s) and very quickly crashes Firefox. I have made this determination because disabling NS causes this to not happen. Screenshot of about:memory while...