[GRASS-dev] [GRASS GIS] #943: wxpython gui hangs after switching to cairo display driver

[GRASS GIS]

#943: wxpython gui hangs after switching to cairo display driver
------------------------------------------+---------------------------------
 Reporter:  epatton                       |       Owner:  grass-dev@…              
     Type:  defect                        |      Status:  new                      
 Priority:  critical                      |   Milestone:  6.4.3                    
Component:  wxGUI                         |     Version:  svn-develbranch6         
 Keywords:  cairo, driver, gui, wxpython  |    Platform:  Linux                    
      Cpu:  All                           |  
------------------------------------------+---------------------------------

Comment(by glynn):

 Replying to [comment:15 hamish]:

 > http://developer.gnome.org/gtk-faq/stable/x505.html.

 The content of that page is nonsense.

 The difference between exit() and _exit() is the the former flushes
 streams (FILE*) and calls any handlers registered with atexit() while the
 latter doesn't. Unless something creates a FILE* for the socket with
 fdopen() (Xlib doesn't), the distinction doesn't matter.

 Terminating a process implicitly close()s all open file descriptors, but
 the underlying object (file, socket, etc) isn't actually closed until no
 process has it open. This is true for an explicit close() call as well as
 an implicit close due to process termination.

 > (another web search mentions that X is perhaps not thread-safe)

 None of this has anything to do with display drivers in general or the
 cairo driver in particular. None of them use GTK, GDK, or threads.

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/943#comment:18>
GRASS GIS <http://grass.osgeo.org>