#1800: v.kernel crashes after long execution
------------------------+---------------------------------------------------
Reporter: arencambre | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 6.4.3
Component: Vector | Version: 6.4.2
Keywords: | Platform: MSWindows 7
Cpu: x86-64 |
------------------------+---------------------------------------------------
A v.kernel run on a dataset with over 700,000 points abruptly crashes
after several hours of processing:
'''v.kernel input=geocoding_after_highway_name_fix@PERMANENT
output=mockingbird_and_central_high_resolution stddeviation=100
STDDEV: 100.000000
RES: 11.176766 ROWS: 4710 COLS: 4495
Writing output raster map using smooth parameter=100.000000.
Normalising factor=64826.350188.
closecell: can't move C:\temp/dallascounty/PERMANENT/.tmp/7128.0
to cell file
C:\temp/dallascounty/PERMANENT/fcell/mockingbird_and_central_high_resolution
Maximum value in output: 2.703527e-002.
(Fri Nov 16 14:26:46 2012) Command finished (59981 sec)'''
Writing output raster map using smooth parameter=100.000000.
Normalising factor=64826.350188.
closecell: can't move C:\temp/dallascounty/PERMANENT/.tmp/7128.0
to cell file
C:\temp/dallascounty/PERMANENT/fcell/mockingbird_and_central_high_resolution
Maximum value in output: 2.703527e-002.
(Fri Nov 16 14:26:46 2012) Command finished (59981 sec)
}}}
#1800: v.kernel crashes after long execution
------------------------+---------------------------------------------------
Reporter: arencambre | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 6.4.3
Component: Vector | Version: 6.4.2
Keywords: | Platform: MSWindows 7
Cpu: x86-64 |
------------------------+---------------------------------------------------
Comment(by arencambre):
I have over 100 GB disk space. I didn't detect much disk utilization
during the run.
Not clear what {{{r.mapcalc "mockingbird_and_central_high_resolution =
rand(0.0, 1.0)"}}} is going to do?
'''mockingbird_and_central_high_resolution''' is the bad output from the
v.kernel run that crashed.
#1800: v.kernel crashes after long execution
------------------------+---------------------------------------------------
Reporter: arencambre | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 6.4.3
Component: Vector | Version: 6.4.2
Keywords: | Platform: MSWindows 7
Cpu: x86-64 |
------------------------+---------------------------------------------------
Comment(by mmetz):
Replying to [comment:3 arencambre]:
> I have over 100 GB disk space. I didn't detect much disk utilization
during the run.
Over 100 GB of free disk space?
>
> Not clear what {{{r.mapcalc "mockingbird_and_central_high_resolution =
rand(0.0, 1.0)"}}} is going to do?
'''mockingbird_and_central_high_resolution''' is the bad output from the
v.kernel run that crashed.
This should tell you if the problem is specific to v.kernel or more
general, because the crash was caused by the GRASS library handling raster
IO, not by v.kernel itself. Therefore the idea is to create a raster map
with the same type and name for the same region settings, but with a
different module in order to find out if the crash in the GRASS library is
specific to v.kernel or more general.
#1800: v.kernel crashes after long execution
------------------------+---------------------------------------------------
Reporter: arencambre | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 6.4.3
Component: Vector | Version: 6.4.2
Keywords: | Platform: MSWindows 7
Cpu: x86-64 |
------------------------+---------------------------------------------------
Comment(by mmetz):
Replying to [comment:5 arencambre]:
> Sorry, meant that I have over 100GB free.
>
> Running
>
{{{
r.mapcalc "mockingbird_and_central_high_resolution = rand(0.0, 1.0)"
}}}
> appeared to be successful
Strange. I tried to reproduce this error with the current release branch
(6.4.svn) and with trunk on a laptop with Fedora Linux 16 64bit, Intel
core i5 at 2.4 GHz and 4 GB RAM.
I followed this tutorial:
#1800: v.kernel crashes after long execution
------------------------+---------------------------------------------------
Reporter: arencambre | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 6.4.3
Component: Vector | Version: 6.4.2
Keywords: | Platform: MSWindows 7
Cpu: x86-64 |
------------------------+---------------------------------------------------
Comment(by arencambre):
CORRECTION: I am reproducing the very, very long execution with the
scenario I emailed you. I am not clear if it still crashes. Regardless, it
appears that the very, very long execution may be the key problem here.
#1800: v.kernel crashes after long execution
------------------------+---------------------------------------------------
Reporter: arencambre | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 6.4.3
Component: Vector | Version: 6.4.2
Keywords: | Platform: MSWindows 7
Cpu: x86-64 |
------------------------+---------------------------------------------------
Comment(by arencambre):
On 6.4.3RC1, the status bar (% complete indicator at bottom of v.kernel
window) actually hasn't budged at all since the 2nd pass started. So we
either have a bug--the status bar doesn't update--or v.kernel is taking
even longer to run than with 6.4.2.