You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
I can't reproduce either with FF 59.0a1 (nightly) and HTTPS-Everywhere 2017.11.21. I have a CPU and (small) memory spike on page load but memory is freed after page load as far as I can tell.
Could it be that this is actually a Firefox problem that is being triggered on some systems by the extreme number of redirects for this ruleset?
In any case the ruleset should be disabled or modified to prevent this from happening. The existing version of the ruleset can be used to continue debugging the memory problem.
Could it be that this is actually a Firefox problem that is being triggered on some systems by the extreme number of redirects for this ruleset?
That would be my guess, but without reproducing it this is hard to debug. I've removed the site from the rulesets in cf1c66c. It shouldn't be too hard to find another ruleset or checkout the old file for memory debugging in the future.
Activity
jeremyn commentedon Dec 4, 2017
It looks like https://psarips.com itself and pretty much all the elements in the page have a redirect loop.
Hainish commentedon Dec 4, 2017
I see this.
about:memoryshould reveal some memory profiling tools to test redirects within Firefox.Bisaloo commentedon Dec 5, 2017
I can't reproduce either with FF 59.0a1 (nightly) and HTTPS-Everywhere 2017.11.21. I have a CPU and (small) memory spike on page load but memory is freed after page load as far as I can tell.
jeremyn commentedon Dec 5, 2017
Could it be that this is actually a Firefox problem that is being triggered on some systems by the extreme number of redirects for this ruleset?
In any case the ruleset should be disabled or modified to prevent this from happening. The existing version of the ruleset can be used to continue debugging the memory problem.
Hainish commentedon Dec 6, 2017
@jeremyn
That would be my guess, but without reproducing it this is hard to debug. I've removed the site from the rulesets in cf1c66c. It shouldn't be too hard to find another ruleset or checkout the old file for memory debugging in the future.
Hainish commentedon Dec 12, 2017
There hasn't been much movement in https://bugzilla.mozilla.org/show_bug.cgi?id=1414091 in the last few days, and this may be unrelated to HTTPS Everywhere (see https://bugzilla.mozilla.org/show_bug.cgi?id=1418815). We should close this if we observe further inactivity on this thread on Bugzilla.
pipboy96 commentedon Mar 28, 2019
I can't see any leak or redirect loops on this website. It fully supports HTTPS.