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 on proj objects when using proj's threadsafe api #4398

Closed
tbonfort opened this issue Jul 18, 2012 · 0 comments
Closed

memory leak on proj objects when using proj's threadsafe api #4398

tbonfort opened this issue Jul 18, 2012 · 0 comments
Assignees
Milestone

Comments

@tbonfort
Copy link
Member

... snip ...

==23873== 520 (328 direct, 192 indirect) bytes in 1 blocks are definitely lost in loss record 37 of 45
==23873==    at 0x4C28BED: malloc (vg_replace_malloc.c:263)
==23873==    by 0x52E08A7: pj_malloc (pj_malloc.c:19)
==23873==    by 0x52DBD39: pj_longlat (pj_latlong.c:61)
==23873==    by 0x52DFBBB: pj_init_ctx (pj_init.c:280)
==23873==    by 0x4F2F81A: msProcessProjection (mapfile.c:1218)
==23873==    by 0x4F2FBDE: msLoadProjectionStringEPSG (mapfile.c:1352)
==23873==    by 0x4F88CEF: msWMSLoadGetMapParams (mapwms.c:1133)
==23873==    by 0x4F9730F: msWMSDispatch (mapwms.c:4859)
==23873==    by 0x4FCA2BF: msOWSDispatch (mapows.c:243)
==23873==    by 0x5037292: msCGIDispatchRequest (mapservutil.c:1631)
==23873==    by 0x401654: main (mapserv.c:257)
... snip ...
@ghost ghost assigned tbonfort Jul 18, 2012
mkofahl pushed a commit to faegi/mapserver that referenced this issue Apr 9, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant