Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

projection "Latitude/Longitude" eats memory #2996

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment
Closed

projection "Latitude/Longitude" eats memory #2996

openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment
Assignees
@openstreetmap-trac
Labels
Component: merkaartor Priority: major Resolution: fixed Type: defect

Comments

@openstreetmap-trac
Copy link

Reporter: chrysn[at]fsfe.org
[Submitted to the original trac issue database at 11.29am, Saturday, 22nd May 2010]

in merkaartor 0.16 prerelease (debian package 0.16~dev1-1), downloading data in "Latitude/Longitude (EPSG:4326)" projection or switching to that projection after data was downloaded in another projection makes merkaartor use up huge quantities of memory (roughly 2gb before it got oom-killed) and not repsond to anything but killing the process.

other projections are not affected.
@openstreetmap-trac openstreetmap-trac self-assigned this Jul 23, 2021
@openstreetmap-trac
Copy link
Author

Author: Koying
[Added to the original trac issue at 6.15pm, Monday, 24th May 2010]

If there was a problem, it should be solved now that coords are store as lat/lon

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@openstreetmap-trac openstreetmap-trac

Labels
Component: merkaartor Priority: major Resolution: fixed Type: defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@openstreetmap-trac