-
-
Notifications
You must be signed in to change notification settings - Fork 332
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] [Windows] Crash of the GRASS-GIS 8.3 v.surf.rst.exe
(OSGeo4W) and Windows module ntdll.dll
#3737
Comments
I wanted to reproduce with an nightly build of the upcoming 8.4, but I can't get an installation launching for now (bugs are filed in). |
The issue occurs also using GRASS-GIS 8.4.0-dev f4d8c62 (OSGeo4W). |
So it's still a valid bug to look into. |
Hmm.. I'm not able to make the module run correctly, but it isn't because of loading a dll or segfault or the sort. I set the projection to WGS84 UTM17N as the data from the issue in the QGIS repo. I don't know what the So, is it true that the data points aren't in the mask, or that's a problem? |
@echoix: does the v.surf.rst manual page example work for you? |
Not really. After making sure I had the north carolina dataset, and found out how to switch to it, it was r.random at the beginning that errored out. It absolutely wanted Adding that, I was able to go up to the first v.surf.rst call. A couple warnings, overshoots, and finishes non-zero.
Details
|
v.surf.rst doesn't crash, with the same inputs and parameters, using GRASS-GIS 7.8.6. |
|
@agiudiceandrea Can you link in that ticket issues #3738 and #3739? I'm not sure my trac credentials are still working right now. |
I have corrected/updated the v.surf.rst example in #3743. |
@echoix, the gdal308/gdal309 OSGeo4W packaging issue is fixed now since grass-dev-8.4-314-f3ccff668-1. |
I installed GRASS-GIS 8.4.0-dev f4d8c62 (grass-dev 8.4-313-f4d8c62ac-1 package) on Windows 10 Home 64-bit using he OSGeo4W Setup also installing the gdal308-runtime package and patching the tree.py file as per #3732, Then I used the GRASS-GIS 8.4.0-dev GUI and executed v.surf.rst with the layers and parameters provided by you. |
It's now fixed in "main". |
tested here with
the first example in the 8.3 manual works on that machine |
trying it with
antivirus/firewall complains about v.surf.rst.exe. could be the original report also related to antivirus/firewall ? |
@hellik, on a Windows 10 Home 64-bit version 1903 build 18362.778 without any antivirus/firewall software running, the issue still occurs using GRASS-GIS version 8.5.0dev 0b0cffc (OSGeo4W): v.surf.rst.exe crashes with the input layers and parameters provided at qgis/QGIS#57523 (comment).
|
Describe the bug
As reported here, running
v.surf.rst
in QGIS on MS Windows 10, results in the following error and the output file is not created:The problem has been traced to
To reproduce
v.surf.rst
algorithm..gpkg
layer in my case)..sdat
raster containing a single polygon. All points are contained within that polygon.All the algorithm parameters
input-points.gpkg
field_3
input-mask-raster.sdat
40.000000
{ default }40
{ default }300
{ default }1.000000
{ default }0.000000
{ default }-1.000000
{ default }0.000100
{ default }auto
{ default }output-raster.sdat
{ sdat file type selected by default }Expected behavior
Creation of a raster with the interpolated RST.
System description
Operating System: Windows 10
GRASS GIS version: 8.3.2
details about further software components
Additional context
I also tried with a different dataset, one for which in Feb. 2023 (possibly QGIS 3.28) the very same procedure had worked perfectly. This time I got the same error described above. It shows that is not a problem with the data, but QGIS/GRASS behaving differently.
The algorithm ran without major problems in Ubuntu (same data, same QGIS version, GRASS 8.3.0)
The text was updated successfully, but these errors were encountered: