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 OSM importer? #32

Closed
ersagunkuruca opened this issue Oct 20, 2016 · 2 comments
Closed

Memory leak in OSM importer? #32

ersagunkuruca opened this issue Oct 20, 2016 · 2 comments

Comments

@ersagunkuruca
Copy link

Admittedly I am trying to import rather large files from here: https://mapzen.com/data/metro-extracts/

A 200MB OSM file of Sydney - Australia uses 4GB of peak memory and takes too much time. After the import Blender uses only 200MB. So I think there should be some memory leak in the importer.

Now I don't mind the time, but I want to import New York City OSM (2GB) and it is impossible with this much of a memory usage. (It goes up to 10GB and crashes.)

Any ideas? (I don't have much experience with Python but maybe I can help with development.)

@vvoovv
Copy link
Owner

vvoovv commented Oct 20, 2016

I am rewriting the add-on from scratch. The new version loads 100 mb OSM file in a minute. The preliminary version (no roofs, no materials) will be published in a couple of weeks.

2Gb is probably too much. Try to cut a smaller area out of the large region.

@vvoovv
Copy link
Owner

vvoovv commented Nov 15, 2016

Give it a try again. I was able to import an OSM file with the size 350 Mb.
Not sure about 2Gb though.

You might want to give it a try again.

@vvoovv vvoovv closed this as completed Nov 19, 2016
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