From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Noam Postavsky Newsgroups: gmane.emacs.bugs Subject: bug#41239: GTK builds crashing in XTread_socket after deleting a frame Date: Sat, 23 May 2020 08:08:42 -0400 Message-ID: <87a71yluph.fsf@gmail.com> References: <83v9kz679v.fsf@gnu.org> <0af1b68c-93d3-2e8b-7810-41d60ef6a2a8@gmx.at> <837dxe61g7.fsf@gnu.org> <9395943c-9690-3d97-067d-77d65c27c187@gmx.at> <83d075uisz.fsf@gnu.org> <87pnazl6hg.fsf@gmail.com> <835zcq7fop.fsf@gnu.org> <87lflklq3e.fsf@gmail.com> <09d44875-b025-4cce-981d-c2f181269091@gmx.at> <87imgoky88.fsf@gmail.com> <87d06vl5le.fsf@gmail.com> <83r1vb189z.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="29651"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.91 (gnu/linux) Cc: 41239@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat May 23 14:09:10 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jcSxh-0007Xl-9K for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 23 May 2020 14:09:09 +0200 Original-Received: from localhost ([::1]:44770 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jcSxg-0004yg-C2 for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 23 May 2020 08:09:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:51182) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jcSxa-0004yN-Dc for bug-gnu-emacs@gnu.org; Sat, 23 May 2020 08:09:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:50258) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jcSxa-0001fY-54 for bug-gnu-emacs@gnu.org; Sat, 23 May 2020 08:09:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jcSxa-0002K9-0e for bug-gnu-emacs@gnu.org; Sat, 23 May 2020 08:09:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Noam Postavsky Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 23 May 2020 12:09:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 41239 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: confirmed Original-Received: via spool by 41239-submit@debbugs.gnu.org id=B41239.15902357318916 (code B ref 41239); Sat, 23 May 2020 12:09:01 +0000 Original-Received: (at 41239) by debbugs.gnu.org; 23 May 2020 12:08:51 +0000 Original-Received: from localhost ([127.0.0.1]:33571 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jcSxO-0002Jk-L8 for submit@debbugs.gnu.org; Sat, 23 May 2020 08:08:50 -0400 Original-Received: from mail-qt1-f194.google.com ([209.85.160.194]:33224) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jcSxN-0002JX-G6 for 41239@debbugs.gnu.org; Sat, 23 May 2020 08:08:49 -0400 Original-Received: by mail-qt1-f194.google.com with SMTP id e16so4573401qtg.0 for <41239@debbugs.gnu.org>; Sat, 23 May 2020 05:08:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version; bh=i36WKOnP0ayLNC4gFhR8GdQ1VoKEs4q8M9AUy+QQimM=; b=TJNB5RNer6gpOM8ItmTIovPx49PRjARjgbI+xWux8R1JQ6ssKeG2QfEreREJmksvu3 wRIRWSr3IbFtPpdGkOmLw9G7tpmzHP7oU7yccdIdWWBBl7DcExvQBnJvQZNn7frDKBsI u5U5HjFfrw7xgYEFy7exkemKE5wUKbQy8db92a2V5lLpNwk2KU2Rz7eEbwV4gxSb0ptL 00wdhFZwoecFgRu7/FdzR9I1ftGbXGF5caupPhvk2mS2gz2r8q93C5/DGOlS75oTAwU1 pUOegV2RRc4yjnBU1pf3PvmboM2n9n5DyjYHfcolTdXOoJctxd/RzecZsMIYOWZ0PuUc r9Vw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version; bh=i36WKOnP0ayLNC4gFhR8GdQ1VoKEs4q8M9AUy+QQimM=; b=MJj5fECmVThkvGhDrz2Z7SDU8ahQ5fk5VbuD0DArofri92wOygNnNhlcUn63wH8RQ5 GGuW4U0pUVwVNdCbPyLYMIZcVKFSsZSbYJrrW1H8ExJ9zG2qdEeuwqJWn/lueFu+5MDw VeGzwtCpt8B1hxBsYpO0BFaRj/qt9S8Syf0t0rIgxeXS45OWl0C9JTCm0qeWXSaQzQTw toaXjNLLmECLvR6JqYKhIG6wiSH6wE+urPEnBrHovTfEuTr4MA4SaP2+tcQceSZM0NwF A83haXYVtLmMEBT2bHWnkL6ZI9q724oEtlfgth4QifCHkr6l4knGCJsotM47tCFBe06+ Nu2A== X-Gm-Message-State: AOAM531cZAwT3HwcRwIXq7y1scYuOjGSzlYxVFfK8DLFjzGthykfeWFL J4N2q4QnGhu9usLsPUx0unRExcWX X-Google-Smtp-Source: ABdhPJwGR66XNGpHXnM6x1YNd0S1LGJ9QtDcKqiuOgUnScLNjK0iIj2By4bJYq39FWIcCgasPanxFQ== X-Received: by 2002:ac8:4906:: with SMTP id e6mr20567655qtq.39.1590235723877; Sat, 23 May 2020 05:08:43 -0700 (PDT) Original-Received: from minid (cbl-45-2-119-47.yyz.frontiernetworks.ca. [45.2.119.47]) by smtp.gmail.com with ESMTPSA id s55sm11062156qtb.92.2020.05.23.05.08.42 (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Sat, 23 May 2020 05:08:43 -0700 (PDT) In-Reply-To: <83r1vb189z.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 23 May 2020 09:21:12 +0300") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:180793 Archived-At: Eli Zaretskii writes: > > Did you succeed in understanding what is that "ID 356" about which it > complains, and why it wasn't found? Not really no, but I have what might be a clue. I can trigger this condition much more reliably (about 3 in 4, instead of 1 in 10; perhaps 1 in 10 times I was doing the following thing by accident), by intentionally moving the mouse over another popup location without letting it pop up, before doing the 'wait for popup and kill frame' procedure. So maybe our cleanup is too thorough in the case where we call xg_prepare_tooltip but the tooltip ends up not being shown. I've tried setting a breakpoint in g_remove_source, but then I'm flooded: it seems to be called every time the mouse moves even a little. martin rudalics writes: >> Ah, I did manage to get it after repeating about 10 times. Following >> https://stackoverflow.com/questions/23199699/glib-critical-source-id-xxx-was-not-found-when-attempting-to-remove-it >> I got a backtrace by putting a breakpoint on g_log. > > How did you do that? Did you build GTK with debugging information? No, just 'break g_log' in gdb works.