Step to reproduce the memory leak

1. From chrome://extensions, open the "Inspect views" for HTTPS Everywhere in a new session.
2. In the console, type redirectCounter. the console should output something like

Object {} // Empty Object

1. Visit https://www.nytimes.com/
2. Repeat Step 2, observe

Object {440: 1, 444, 1}

1. Repeat Step 3-4, observe redirectCounter keep growing without sign of removing previous items

Object {440: 1, 444: 1, 598: 1, 601: 1, 632: 1, 635: 1}

This affect long lasting browsing sessions.

UPDATE On Mixed Content pages, HTTP request are blocked by MCB from the browser. It is necessary to listen on both HTTP & HTTPS connection to resolve the memory leak (Assuming no "Block all unencrypted requests"). thanks.

P.S. I expected browser to handle redirect loops automatically, however, I am not really sure about the case when an extension rewrite URLs.