Skip to content
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
This repository was archived by the owner on Nov 6, 2023. It is now read-only.

Chrome: HTTPS Everywhere is incredibly slow #12

Closed

Description

@semenko

[Chrome specific]

I'll be sending a bunch of pull requests over the next few days. Just wanted to open a tracking bug.

HTTPS Everywhere takes an enormous amount of CPU time, which you can see from both the Task Manager and performance profiling in Chrome. The taskbar even on fast machines frequently shows "Waiting for extension HTTPS Everywhere …".

The current performance even makes HTTPS Everywhere borderline unusable on underpowered machines (e.g. some Chromebooks).

Activity

  1. diracdeltas commented on Dec 20, 2013

    @diracdeltas
    Contributor

    Sweet. :)

    I bet some of those patches can get backported to the FF version too.

    Nick, do you have thoughts on a better data structure for the rulesets? Like, something better than the ginormous XML file that gets loaded into memory. Could try compiling it to JSON, or even using a sqlite database.

  2. semenko commented on Dec 20, 2013

    @semenko
    ContributorAuthor

    @diracdeltas Haven't even looked at the rulesets yet, but JSON is likely a much better idea going forward. :)

  3. jsha commented on Dec 10, 2014

    @jsha
    Member

    Is this issue still live?

  4. semenko commented on Dec 10, 2014

    @semenko
    ContributorAuthor

    Hm -- probably not. I'd still love to switch to DWR (issue #132) if Chrome pledged to move that to stable...

  5. added a commit that references this issue on Sep 23, 2015
  6. gopi-ar commented on Mar 6, 2016

    @gopi-ar

    Bump. Chrome on my brand new mac slowed down to a crawl (tabs opening, scrolling, etc), all because of this extension! Disabling it made it all good again!

  7. bdzs commented on Mar 9, 2016

    @bdzs

    Yeah I know this is a closed issue but it slows down Chrome too much. Basically I had to disable it because loading sites and the overall performance of the browser was just too low.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions