le jeu 21-03-2002 à 13:12, Paul Davis a écrit : > >Another solution is to put every calls that are made into thread in > >g_idle_add functions. I know that it would prevent threads problems, but > >I would like to know why something that perfectly worked with GTK1 has > >so much problems now and always segfaults as calls to GTK functions were > >not protected by the GDK lock? I do not understand that simple fact. > > perhaps the internals of GTK/GDK has changed the ultimate ordering of > calls to the X server, so things you were doing without locks are > causing async problems. the fact that it worked under GTK+ 1.2 doesn't > mean anything - its been said over and over and over that you cannot > have multiple threads calling *any* GTK or GDK or X functions without > lock protection. if it worked before, that was just luck and relied on > the internal structure of GTK/GDK, much of which has now changed. > All things Im doing from threads are protected by the lock... But I noticed that all those crashes disappeared once I ran GnomeMeeting under the same user as the gnome session. If I run GnomeMeeting under the same user as the gnome session, I get no crashes, no problem. Except one : if I cover the GnomeMeeting window several times in a row and quickly by another window, it crashes when refreshing the drawing area. It can also crash when changing the GTK theme. I'll try to investigate further, but I have no idea where. And I don't think anymore that this kind of thing is a bug in GnomeMeeting. > --p > > -- _ Damien Sandras (o- GnomeMeeting - H.323 Video-Conferencing application - //\ web: http://www.gnomemeeting.org/ v_/_ FOSDEM 2002 - Free Software and Open Source Developers Meeting - web: http://www.fosdem.org/
Attachment:
signature.asc
Description: This is a digitally signed message part