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

Virtual memory leak in legacy geo datasets? #259

Open
gfr10598 opened this issue Jun 4, 2019 · 1 comment
Open

Virtual memory leak in legacy geo datasets? #259

gfr10598 opened this issue Jun 4, 2019 · 1 comment
Labels
backlog P2

Comments

@gfr10598
Copy link
Contributor

gfr10598 commented Jun 4, 2019

It looks like virtual memory size gradually creeps up when there are requests for annotations from legacy datasets. Virtual memory is flat when there are only geolite2 requests.

The resident memory is fairly stable - just oscillating with garbage collection.
@autolabel autolabel bot added the review/triage Team should review and assign priority label Jun 4, 2019
@gfr10598
Copy link
Contributor Author

gfr10598 commented Jun 4, 2019

Peter points out this is probably because the mmap is happening repeatedly, instead of just once.

@autolabel autolabel bot removed the review/triage Team should review and assign priority label Jun 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
backlog P2
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gfr10598 @mehtab11