Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

r.in.pdal crashes on Windows during rasterization

Abierto
  • ¿Algo no está bien?
#7,828 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
c, python
Área
data

Línea de trabajo

Start by tracing the r.in.pdal rasterization and point-processing path, especially the code reached after “Scanning points...”; the issue does not name source files or tests. Reproduce on Windows with the supplied four-point LAS command, then compare against the working extent and vector-import paths. Done means rasterization completes without the access violation on the reported Windows builds.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug

On Windows, r.in.pdal consistently crashes with an access violation when it starts processing points.

Environment

Tested with the official conda-forge GRASS 8.5 build:

grass          8.5.0   py311h7721632_1
libpdal-core   2.10.0  h1f91b6b_0

Also tested with the current GRASS 8.6 development conda build:

grass-dev      dev     py311h82bb817_0
libpdal-core   2.10.2  hd7c2432_4

Windows 11, Python 3.11, micromamba/conda environments.

Reproducer
r.in.pdal -eno input="synthetic_test.las" output=synthetic_test resolution=1

Output:

Reading data...
Overriding projection check and assuming that the CRS of input matches the project's CRS
Running PDAL algorithms...
Scanning points...

The process then exits immediately.

echo %ERRORLEVEL%

returns:

-1073741819

which corresponds to Windows exception 0xC0000005 (access violation).

Tests performed

The same crash occurs with:

  • official conda-forge GRASS 8.5
  • GRASS 8.6dev conda build
  • libpdal-core 2.10.0 and 2.10.2
  • COPC .laz
  • the same data converted to ordinary .las
  • method=mean
  • method=n
  • a minimal GRASS environment without QGIS

The issue does not appear to be related to the input data. I also created a synthetic LAS containing only four simple XYZ points, and r.in.pdal crashes in exactly the same way.

Other PDAL-related operations on the same files work correctly:

pdal info --metadata file.las

works.

r.in.pdal -go input=file.las

works and returns the extent.

v.in.pdal -oc input=file.las output=test spatial=...

also works successfully with exit code 0.

So the failure appears to be specific to the rasterization/point-processing path of r.in.pdal on Windows, rather than PDAL file reading or GRASS-PDAL integration in general.

Lenguaje dominante
C
Estrellas
1.2k
Forks
447
Merge medio
1 d 18 h
PR fusionados (30 d)
75

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de OSGeo/grass

Todos los issues de OSGeo/grass

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.