[GRASS-dev] [GRASS GIS] #2151: g.gui.* modules which use temporal framework leave processes after exiting

GRASS GIS trac at osgeo.org
Wed Jan 1 16:47:47 PST 2014


#2151: g.gui.* modules which use temporal framework leave processes after exiting
--------------------------------------------+-------------------------------
 Reporter:  annakrat                        |       Owner:  grass-dev@…              
     Type:  defect                          |      Status:  new                      
 Priority:  normal                          |   Milestone:  7.0.0                    
Component:  Python                          |     Version:  svn-trunk                
 Keywords:  g.gui.animation, temporal, RCP  |    Platform:  Linux                    
      Cpu:  All                             |  
--------------------------------------------+-------------------------------

Comment(by huhabla):

 I tried to solve the problem by registering a function at exit that
 explicitly terminates the subprocesses. I added this code to
 lib/python/temporal/core.py:

 {{{
 #!python
 import atexit

 def stop_subprocesses():
     """!Stop the messenger and C-interface subprocesses
     """
     global message_interface
     global c_library_interface
     if message_interface:
         message_interface.stop()
     if c_library_interface:
         c_library_interface.stop()

 atexit.register(stop_subprocesses)
 }}}

 This works for temporal modules, but not for the GUI.

 The registered function is not be called at exit when g.gui.animate
 terminates!
 How does the GUI framework terminates so that this functionality does not
 work?

 Besides of that, it seems to me that tgis.init() is called several time
 when g.gui.animate is opened and a space time raster dataset is chosen for
 visualization. It hope that this can be reduced to a single tgis.init()
 call?

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/2151#comment:2>
GRASS GIS <http://grass.osgeo.org>



More information about the grass-dev mailing list