search

tilemill-project / tilemill

TileMill is a modern map design studio
https://tilemill-project.github.io/tilemill/
BSD 3-Clause "New" or "Revised" License
3.12k stars 527 forks source link

error: child process failed with code 3 #2214

Open bambax opened 10 years ago

bambax commented 10 years ago

I get the above error on 0.10.1 when trying to add a layer from a postgresql database. TileMill runs on Windows XP; the postgresql database runs on Debian in VirtualBox on the same machine (created by osm2pgsl). The connection to the database works fine when using pgAdmin from the Windows host.

Here are TileMill logs: [tilemill] Started [Server Tile:20008]. [tilemill] Plugin [editor] loaded. [tilemill] Plugin [fonts] loaded. [tilemill] Plugin [templates] loaded. [tilemill] Started [Server Core:20009]. [tilemill] Client window created (pass --server=true to disable this) [tilemill] [millstone] processing style 'style.mss' [tilemill] [millstone] processing layer 'countries' [tilemill] [millstone] processing layer 'roads' [tilemill] [millstone] processing layer 'railways' [tilemill] [millstone] processing layer 'network' [tilemill] [millstone] finished processing 'C:\Documents and Settings\EB\Documents\MapBox\project\test' [tilemill] [millstone] processing style 'layer' [tilemill] Error: child process: "tile" failed with code "3" [tilemill] Closing child process: core (pid:552) Exiting TileMill due to fatal error...

springmeyer commented 10 years ago

You are likely running out of memory. How big is this query?

bambax commented 10 years ago

It was the road layer for France. The project already included layers from shapefiles, and although those were hidden, apparently they did consume memory.

I was able to open the road layer in a new project, without triggering the error.

I then tried to install OSM Bright, but just opening the project immediately crashes TileMill with the same code '3'.

What is the free memory amount recommended to run TileMill for a country such as France?

springmeyer commented 10 years ago

OSM bright error likely has to do with an error unzipping the shapefiles. The solution to that problem is to unzip them ahead of time.