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

Complaints about lack of a map pool #83

Closed
mojodna opened this issue Jul 6, 2014 · 6 comments
Closed

Complaints about lack of a map pool #83

mojodna opened this issue Jul 6, 2014 · 6 comments

Comments

@mojodna
Copy link
Contributor

mojodna commented Jul 6, 2014

I've been seeing this a bunch lately, initially when using TileMill@HEAD and now when running tilelive-mapnik's tests:

render: this map appears to be in use by 1 other thread(s) which is not allowed. You need to use a map pool to avoid sharing map objects between concurrent rendering

@springmeyer
Copy link
Contributor

does it go away if you run node-mapnik head with this fix: mapnik/node-mapnik@21253f7 ?

@mojodna
Copy link
Contributor Author

mojodna commented Jul 15, 2014

Unclear (partially because I hosed and unhosed my mapnik install). I'll continue to keep an eye out for it now that I think I've got that patch.

@springmeyer
Copy link
Contributor

If your external mapnik install is hosted, you can get a quick source install out by doing ./scripts/build_against_sdk.sh

@mojodna
Copy link
Contributor Author

mojodna commented Jul 15, 2014

Good to know. I wound up brew editing the mapnik formula and pointing at the 2.3.x branch. I was initially seeing segfaults with node-mapnik, but make clean, etc. there seemed to help.

@springmeyer
Copy link
Contributor

hmm, noting that this has started showing up in tilemill too: https://github.com/mapbox/tilemill/issues/2371

@springmeyer
Copy link
Contributor

confirmed that this will be solved by upcoming node-mapnik v1.4.12 tag.

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