[pdal] Debugging std::bad_alloc

Andrew Bell andrew.bell.ia at gmail.com
Sat May 13 10:40:06 PDT 2017


Bad alloc means that you're out of memory.  I'm sorry but I don't know
anything about configuring swap space for docker, but in order to get
things to run, that's what you need.  The raster is kept in memory and if
you have a big raster you need lots of memory.

Hope that helps,

On Sat, May 13, 2017 at 12:16 PM, James Harrison <james at talkunafraid.co.uk>
wrote:

> Hi all,
>
> I'm running PDAL in Docker with a simple pipeline to write a single
> dimension with the GDAL writer. The LAZ being consumed as input is
> PDAL-generated 1.4 LAS, with the source file (LAS 1.2) to that process
> coming from the TerraSolid/Bentley Microstation toolset.
>
> I'm using Docker, the latest PDAL image (Docker SHA256 4d1b5..., PDAL
> commit aea5bb) and have plenty of disk space free at least in the host's
> domain.
>
> All is well on the LAZ side, and ground.laz parses OK (with pdal info,
> running in Docker). The LAZ in question has 46,468,399 points and a
> number of dimensions. A smaller file runs through this process correctly.
>
> My pipeline is thus:
>
> {
>   "pipeline": [
>     "/output/ground.laz",
>     {
>       "type": "writers.gdal",
>       "resolution": 0.015,
>       "radius": 0.035,
>       "window_size": 1,
>       "filename": "/output/layer-Red.tif",
>       "output_type": "idw",
>       "dimension": "Red"
>     }
>   ]
> }
>
> If I run PDAL on this file I get an error after a little while - even
> with verbosity 8, nothing is emitted:
> [james at hostname laser_coloured_matched]$ docker run -it --rm -v
> /tmp/lidar-tmp-1/las2tiff/210000_396000/:/output pdal/pdal:latest pdal
> --developer-debug pipeline /output/layer-Red.json
> terminate called after throwing an instance of 'std::bad_alloc'
>   what():  std::bad_alloc
>
> I'm at a bit of a loss as to how to go about getting more meaningful
> error messages out of PDAL, hence the ML post rather than GH issue. Am I
> missing a trick to produce more debug messages/output? Is this a known
> problem with non-obvious causes like Docker doing something silly with
> temporary storage? Or am I being an idiot? :-)
> --
> Cheers,
> James Harrison
>
>
> _______________________________________________
> pdal mailing list
> pdal at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/pdal
>



-- 
Andrew Bell
andrew.bell.ia at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pdal/attachments/20170513/085d2bf5/attachment.html>


More information about the pdal mailing list