Resources are not freed properly

[uhlat]

When downloading big tilesets, the system will slowly run out of RAM since somewhere in the implementation (or external dependencies) resources are not free properly. See Screenshot for an example.

[mojodna]

Can you share the command you're using (or a filtered version of it) to help me determine which modules are in play?

Thanks.

[uhlat]

sure, here you go:
tl copy -z 10 -Z 10 -b "-180 -90 0 90" tmstyle:///home/myhome/MapBox/streets.tm2 mbtiles:///home/myhome/Tiles/streets_10_-180_0.mbtiles

[mojodna]

Great, thanks. It's going to take me some time to get to this, as it involves firing up the heap snapshot processor, etc.

[jrunkel]

Any update on this matter? I have the same problem. Copying from tmstyle to mbtiles as well.

[mojodna]

I haven't had a chance to look into this yet, sorry.

[morganmcc]

I think I just ran into this trying to generate a map of just the US based on a MapBox style. The command was very similar to what Uhlat used.
npm-exec tl copy -z 4 -Z 13 -b "-135.4395 16.3834 -56.4258 54.0078" tmstyle:///home/mccollm1/Documents/MapBox/MapBoxLight.tm2 mbtiles:///home/mccollm1/dev_monitor/tessera/MonitorMap_us.mbtiles

I left it running and it got most of the way through zoom level 12 before bailing:
12/1064/1786 103
FATAL ERROR: CALL_AND_RETRY_2 Allocation failed - process out of memory
Aborted (core dumped)

[morganmcc]

Forgot to mention I am using version 0.5.3.

[mojodna]

@morganmcc which version of Node and which OS? (Probably doesn't matter, but it might make a difference.)

[morganmcc]

I'm on Ubuntu 14.0.4 using node v0.10.40. I ran it again yesterday and periodically kept an eye on memory resources. It wasn't in any way a thorough test, but I did not notice any steady increase in memory. So, if there is a leak, it is a small one. Not sure if it helps, but I did notice that there are occasional CPU spikes and it seems to pause on a particular tile but then the CPU drops again and the log of tile numbers starts up again. Maybe that is just periodic cache cleanup?

What version of node have you been working with in your environment? I could try that one.