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

memory not being released #63

Closed
nilsnolde opened this issue Mar 3, 2022 · 3 comments
Closed

memory not being released #63

nilsnolde opened this issue Mar 3, 2022 · 3 comments

Comments

@nilsnolde
Copy link
Owner

nilsnolde commented Mar 3, 2022

@nmalasevic just encountered a serious flaw in our image, not being present in the upstream valhalla image:
valhalla/valhalla#3556 (comment)

also sounds pretty terrible to debug.. open for suggestions!:)

@nmalasevic
Copy link

Sounds like every request is behaving like an instance of it's own, so cached memory is not being reused in case of subsequent requests (same request).

@nilsnolde
Copy link
Owner Author

the way the tile cache works it shouldn't be possible (I think), also I don't see how that should be caused by the way we run things in the container. I guess it's some weird interaction of the docker entrypoint script and docker.. maybe the exec "$@" line, no idea.. will poke around a bit soon-ish.

@nilsnolde
Copy link
Owner Author

See discussion in #81

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

2 participants