Skip to content
This repository has been archived by the owner on Mar 23, 2023. It is now read-only.

[Bug] ArkClient Helper spiking CPU (macOS High Sierra) #364

Closed
nlpthk opened this issue Oct 24, 2017 · 3 comments
Closed

[Bug] ArkClient Helper spiking CPU (macOS High Sierra) #364

nlpthk opened this issue Oct 24, 2017 · 3 comments

Comments

@nlpthk
Copy link

nlpthk commented Oct 24, 2017

Recently my MacBook's fans have been going off and upon inspection via the Activity Monitor, "ArkClient Helper" has been on the top of the CPU processes list

@krau612
Copy link

krau612 commented Oct 24, 2017

This is most likely related to Issue #358 which is resolved by PR #357 .

Can you do me a favor to help confirm this? Can you:

  1. Record the CPU usages of ArkClient and ArkClient Helper
  2. Close the client
  3. Force quit all instances of ArkClient and ArkClient Helper in the Activity Monitor
  4. Open the client
  5. Record the CPU usages of ArkClient and ArkClient Helper

Essentially, there's a process that continues to run after you close the client. If you have opened and closed the client multiple times without restarting your computer, then multiple instances of this process will be running in the background.

@j-a-m-l
Copy link
Contributor

j-a-m-l commented Dec 7, 2017

Please, @nlpthk could you confirm that this problem is fixed on the last version?

@nlpthk
Copy link
Author

nlpthk commented Dec 8, 2017

Yup! Haven't experienced the problem with 1.4.3:)

@j-a-m-l j-a-m-l closed this as completed Dec 8, 2017
alexbarnsley pushed a commit that referenced this issue Dec 3, 2018
* feat: add loader indicator
* fix: undefined last ticker
* feat: add initial table pagination
* fix: resolve travis
* chore: update client and add vue-spinner
* refactor: add query params in fetchTransactions
* fix: improve tests
* chore: fetch transactions according to the current page
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants