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.

Sign up for GitHub

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

Jump to bottom

WebKitNetworkProcess CPU consumption #55

Open
peterzen opened this issue Apr 12, 2020 · 0 comments · Fixed by #56
Open

WebKitNetworkProcess CPU consumption #55

peterzen opened this issue Apr 12, 2020 · 0 comments · Fixed by #56
Labels
bug Something isn't working golang
Milestone
MVP

Comments

@peterzen
Copy link
Owner

After some startups,WebKitNetworkProcess eats 100% CPU. Can't always reproduce - it happens around 50% or so of the time, not after all startups.

May have something to do with a race condition in exchangeratebot/coingecko.go but needs further investigation/profiling.

32321 peter     20   0 82.425g  50980  37108 R  98.7  0.3   0:31.05 WebKitNetworkProcess
@peterzen peterzen added bug Something isn't working golang labels Apr 12, 2020
@peterzen peterzen added this to the MVP milestone Apr 12, 2020
@peterzen peterzen mentioned this issue Apr 12, 2020
Merged
@peterzen peterzen reopened this Apr 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working golang
Projects
None yet
Milestone
MVP
Development

Successfully merging a pull request may close this issue.

exchangeratebot initialization race fix peterzen/kohola
1 participant
@peterzen