[Bugs] #3670 Browse IMME: Browse segfaults when closing

[Sugar Labs Bugs]

#3670: Browse segfaults when closing
--------------------------+-------------------------------------------------
    Reporter:  erikos     |          Owner:  erikos       
        Type:  defect     |         Status:  new          
    Priority:  Immediate  |      Milestone:  0.96         
   Component:  Browse     |        Version:  0.96.x       
    Severity:  Critical   |       Keywords:  12.1.0, patch
Distribution:  OLPC       |   Status_field:  Assigned     
--------------------------+-------------------------------------------------

Comment(by humitos):

 Replying to [comment:1 erikos]:
 > {{{
 > Program received signal SIGSEGV, Segmentation fault.
 > }}}

 I don't see the "Segmentation fault." on the log. This is what I get
 {{{
 Terminated by signal 11, pid 429 data (None, <open file '<fdopen>',
 mode 'w' at 0x96a5020>, 'b3e26c69860201b3c492994bb7504a3980ea963c')
 }}}

 Signal 11 is the same as SIGSEGV. Where did you get that information?

 After aplying the patch I get this:
 {{{
 Exited with status 0, pid 1480 data (None, <open file '<fdopen>',
 mode 'w' at 0x96a5020>, 'a67b0adeb68f644d390346936c1be85e828b4338')
 }}}

 Well, reading [http://faq.pygtk.org/index.py?req=show&file=faq20.006.htp
 this document] (it's for gtk2, but it's the same concept) I found that if
 we want to update the GIU by another thread we must use
 {{{GObject.threads_init()}}} and then {{{GObject.idle_add()}}} but it
 doesn't say what's up if we use {{{idle_add}}} without {{{threads_init}}}
 [http://git.sugarlabs.org/browse/mainline/blobs/master/edittoolbar.py#line80
 which is our case now][1] that we removed {{{GObject.threads_init()}}}

 [1] I'm not sure what is the function of that line

-- 
Ticket URL: <http://bugs.sugarlabs.org/ticket/3670#comment:7>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system