Matthew Lye wrote: > I just experienced a similar crash running revision 14708 (that's > after the changes, right?), which occurred when I selected a a whole > bunch of browse entries and then tried, erroneously, to close them > using the 'close' button, rather than selecting from the pop-up > menu.
This does not seem related to the other crash you've reported before. > No significant prior message. Given the nesting depth of gtk frames, > it's hard to believe that GTKG could be at all responsible, rather > than non-optimizable mathematical shortcuts in GTK1 or something, but > I have no clue. It looks like an attempt to deliver a signal after the widget has been destroyed and it also looks more like a bug in Gtk+ 1.2 itself but I cannot reproduce this, so it's rather hopeless. -- Christian ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ gtk-gnutella-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
