[GRASS-dev] [GRASS GIS] #613: clean_temp: not safe for concurrent use
GRASS GIS
trac at osgeo.org
Fri Aug 31 20:55:48 PDT 2018
#613: clean_temp: not safe for concurrent use
----------------------+--------------------------------------
Reporter: hamish | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.6.0
Component: Startup | Version: 6.4.0 RCs
Resolution: | Keywords: clean_temp init grass.py
CPU: All | Platform: All
----------------------+--------------------------------------
Changes (by wenzeslaus):
* keywords: clean_temp => clean_temp init grass.py
* milestone: 6.4.6 => 7.6.0
Comment:
This still might be an issue. `clean_temp()` (which calls `clean_temp`) is
called on [source:grass/trunk/lib/init/grass.py?rev=73199#L2037 line 2040]
while mapset is set and ready later on
[source:grass/trunk/lib/init/grass.py?rev=73199#L2079 line 2087]. Same in
7.0 and trunk (7.7). (Now I have second thoughts about closing #1286, but
if it is an issue (location being set, but possibly garbage), it is really
this one anyway.)
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/613#comment:3>
GRASS GIS <https://grass.osgeo.org>
More information about the grass-dev
mailing list