{"action":"created","issue":{"url":"https://api.github.com/repos/EFForg/https-everywhere/issues/1775","labels_url":"https://api.github.com/repos/EFForg/https-everywhere/issues/1775/labels{/name}","comments_url":"https://api.github.com/repos/EFForg/https-everywhere/issues/1775/comments","events_url":"https://api.github.com/repos/EFForg/https-everywhere/issues/1775/events","html_url":"https://github.com/EFForg/https-everywhere/issues/1775","id":81373246,"number":1775,"title":"Does HTTPS Everywhere takes too much memory on Chrome?","user":{"login":"bcroq","id":130780,"avatar_url":"https://avatars.githubusercontent.com/u/130780?v=3","gravatar_id":"","url":"https://api.github.com/users/bcroq","html_url":"https://github.com/bcroq","followers_url":"https://api.github.com/users/bcroq/followers","following_url":"https://api.github.com/users/bcroq/following{/other_user}","gists_url":"https://api.github.com/users/bcroq/gists{/gist_id}","starred_url":"https://api.github.com/users/bcroq/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bcroq/subscriptions","organizations_url":"https://api.github.com/users/bcroq/orgs","repos_url":"https://api.github.com/users/bcroq/repos","events_url":"https://api.github.com/users/bcroq/events{/privacy}","received_events_url":"https://api.github.com/users/bcroq/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-05-27T09:46:05Z","updated_at":"2015-05-27T16:46:28Z","closed_at":null,"body":"I use HTTPS Everywhere Chrome 43.0.2357.65 (64-bit Linux) and the extension eats a little more than 100MB of memory. Isn't it too much for this kind of extension?"},"comment":{"url":"https://api.github.com/repos/EFForg/https-everywhere/issues/comments/105989630","html_url":"https://github.com/EFForg/https-everywhere/issues/1775#issuecomment-105989630","issue_url":"https://api.github.com/repos/EFForg/https-everywhere/issues/1775","id":105989630,"user":{"login":"jsha","id":220205,"avatar_url":"https://avatars.githubusercontent.com/u/220205?v=3","gravatar_id":"","url":"https://api.github.com/users/jsha","html_url":"https://github.com/jsha","followers_url":"https://api.github.com/users/jsha/followers","following_url":"https://api.github.com/users/jsha/following{/other_user}","gists_url":"https://api.github.com/users/jsha/gists{/gist_id}","starred_url":"https://api.github.com/users/jsha/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jsha/subscriptions","organizations_url":"https://api.github.com/users/jsha/orgs","repos_url":"https://api.github.com/users/jsha/repos","events_url":"https://api.github.com/users/jsha/events{/privacy}","received_events_url":"https://api.github.com/users/jsha/received_events","type":"User","site_admin":false},"created_at":"2015-05-27T16:46:28Z","updated_at":"2015-05-27T16:46:28Z","body":"@bcrow: Yes, my gut feeling is that HTTPS Everywhere can and should be optimized for better memory and CPU use. We haven't had the time to do it yet, but would very much welcome help from someone who is experienced at profiling extensions.\r\n\r\nThe uBlock number you quote is actually encouraging! HTTPS Everywhere has 14.5k 'rulesets', but each ruleset contains many targets and rules, which are presumably more akin to uBlock's filters. There are 39361 rules and 41287 targets, for a total of ~80k entities. The memory usage for those entities sounds proportional to uBlock, which is a surprise to me. Still, we can probably do a better job of keeping inactive rulesets out of memory."}}