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

oauth2: Resolve memory leak in gorilla/sessions #1374

Merged
merged 1 commit into from
Apr 20, 2019
Merged

oauth2: Resolve memory leak in gorilla/sessions #1374

merged 1 commit into from
Apr 20, 2019

Conversation

aeneasr
Copy link
Member

@aeneasr aeneasr commented Apr 19, 2019

Closes #1363

Closes #1363

Signed-off-by: aeneasr <aeneas@ory.sh>
Copy link
Contributor

@aaslamin aaslamin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🏆

@aaslamin
Copy link
Contributor

aaslamin commented Apr 19, 2019

Would be nice if we had nightly (or weekly if it is $$$$$) load tests for common workflows running in CI so we can catch major regressions faster.

Not offering any solutions to 🔝yet, just something to think about!

@aeneasr
Copy link
Member Author

aeneasr commented Apr 20, 2019

So we do have a benchmark thingy running but it doesn't check for memory leaks and it also didn't run against the OAuth2 Auth endpoint. Maybe we can enhance that script to include that?

@aeneasr aeneasr merged commit e745aee into master Apr 20, 2019
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

Successfully merging this pull request may close these issues.

Memory leak with jaeger tracing enabled
2 participants