This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
UI causes Parity to consume too much CPU #3240
Comments
Some work have been done in #3227 to fix these. Will make a smaller PR from this one. |
ngotchac
added a commit
that referenced
this issue
Nov 17, 2016
ngotchac
added a commit
that referenced
this issue
Nov 17, 2016
ngotchac
added a commit
that referenced
this issue
Nov 17, 2016
Only refresh statuses when on Status Page for some statuses (eg. hashrate)
Merged
ngotchac
added a commit
that referenced
this issue
Nov 18, 2016
ngotchac
added a commit
that referenced
this issue
Nov 18, 2016
ngotchac
added a commit
that referenced
this issue
Nov 19, 2016
ngotchac
added a commit
that referenced
this issue
Nov 21, 2016
ngotchac
added a commit
that referenced
this issue
Nov 21, 2016
ngotchac
added a commit
that referenced
this issue
Nov 21, 2016
ngotchac
added a commit
that referenced
this issue
Nov 21, 2016
ngotchac
added a commit
that referenced
this issue
Nov 21, 2016
jacogr
pushed a commit
that referenced
this issue
Nov 23, 2016
* Don't auto-subscribe for contracts #3240 * Smarter Balance : don't re-instantiate contracts, fetch tokens #3240 * Smarter Balance Tokens fetching (update image when needed) #3240 * Attaching to TokenReg Events instead of fetching for each block #3240 * Unsubscribe from shapeshit... #3240 * Unsubscribe from EthFilter if used once (resolved) #3240 * Remove warning * PR review fix * Typo * Better contract JS API : one subscribe for all #3546 * Fixed test
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Both Parity & Chrome shows higher than normal CPU usage when the app is open. Check -
The text was updated successfully, but these errors were encountered: