Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory and Processor Performance #12

Open
mattscully opened this issue Dec 11, 2012 · 3 comments
Open

Memory and Processor Performance #12

mattscully opened this issue Dec 11, 2012 · 3 comments

Comments

@mattscully
Copy link

I have enjoyed using this extension; thank you! I wanted to let you know I have noticed some performance issues. For example, when I view the Chrome Task Manager after leaving it running over the weekend, Trello Points was taking 1.2GB of memory. Also, the processor utilization seems to constantly sit around 10%-13% (refresh seconds is set to 1). Has anyone else reported this? Please let me know if there is anything I can do to provide more information.

--matt

@jgraglia
Copy link
Owner

Thx for you comment!
The memory leak you find is really bad. I will try to get a fix for that.

Points for Trello use a backgound timer to update points on all cards. By default the cycle of this timer is every 2 seconds. This is my main suspect for the mem leak
As a workaround could you try to increase the cycle to sth like 30 seconds.? il will lower the mem consumption.
You can do that in the options pane of the extension.
(To get the options pane : right click on extension icon near your adresse bar > Options
or Chrome Menu > Tools > Extensions)

@mattscully
Copy link
Author

Thanks! I changed the refresh time to be 30 seconds, so hopefully that will help.

@thecodefish
Copy link

I don't know if this was ever looked at, but I've just installed the extension and I'm noticing growing memory usage over time still. Nothing like the 1.2GB above, but after leaving it running for a while I noticed the extension using a little over 100mb, and steadily increasing every time it refreshed (by a very small amount, but still). It doesn't appear to be releasing anything when refresh completes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants