[Tile-serving] [openstreetmap/osm2pgsql] Segmentation fault (core dumped) (Issue #2079)

[Jochen Topf]

Segmentation faults are almost always a sign of not having enough memory. Especially with this happening later in the process when you used a bigger machine. Figuring out how much memory something will use or is using is not straightforward. It might well be that everything looks fine and the next thing the program needs twice as much memory as before. So I`d recommend testing with a larger machine.

You can also try with `--disable-parallel-indexing --number-processes=1`. This will make osm2pgsql do less stuff at the same time possibly reducing its memory footprint somewhat. (But processing will take longer.)

That being said, of course there could be a different problem there. If you want to pursue this, create a debug build and look at the core dump created by the segmentation fault, specifically we need to backtrace do diagnose further.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/osm2pgsql/issues/2079#issuecomment-1720817537
You are receiving this because you are subscribed to this thread.

Message ID: <openstreetmap/osm2pgsql/issues/2079/1720817537 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20230915/4f976682/attachment-0001.htm>