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 leak in the tiler #20

Open
ppawel opened this issue Jan 4, 2013 · 1 comment
Open

Memory leak in the tiler #20

ppawel opened this issue Jan 4, 2013 · 1 comment
Labels

Comments

@ppawel
Copy link
Owner

ppawel commented Jan 4, 2013

OOM killer kicked in again tonight... Some logs:

D, [2013-01-04T02:44:57.257553 #7989] DEBUG -- : W 152813734 (2)
D, [2013-01-04T02:44:57.280255 #7989] DEBUG -- :   tile_count = 2147504146
D, [2013-01-04T02:55:37.107015 #7989] DEBUG -- :   tiles_to_check = 1126144
D, [2013-01-04T03:01:23.219906 #7989] DEBUG -- :   Processing 2252464 tile(s)...

And then it's dead.

@ppawel
Copy link
Owner Author

ppawel commented Jan 10, 2013

I think it is not really this specific changeset (although it is huge) but some kind of memory leak in the tiler. When it runs on zark through the night you can clearly see memory used growing and growing until the OOM killer kills the tiler.

http://munin.openstreetmap.org/openstreetmap/zark.openstreetmap/memory.html

Not sure what this could be. GEOS objects seem to be automatically released. What else could it be? Need to investigate further.

Tried using heap_dump gem to check the heap contents but it requires Ruby newer than zark's 1.9.1...

ppawel added a commit that referenced this issue Jan 12, 2013
ppawel added a commit that referenced this issue Jan 20, 2013
ppawel added a commit that referenced this issue Jan 21, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant