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

Workshop suggestions #39

Open
bflanigan opened this issue Jul 18, 2017 · 0 comments
Open

Workshop suggestions #39

bflanigan opened this issue Jul 18, 2017 · 0 comments

Comments

@bflanigan
Copy link

  1. How would a memory leak or goroutine leak look like in pprof or the trace tool?
  2. How would a cancelled context that cascades its way through "many" child goroutines look like in pprof or the trace tool?
  3. Tracking down a memory leak - what are best practices for avoiding mem leaks? Provide examples of blatant and not so blatant ways to leak memory.
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

1 participant