From: Brian Burns <bburns.km@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Joseph Mingrone <jrm@ftfl.ca>, 22214@debbugs.gnu.org
Subject: bug#22214: 25.0.50; lock up with gui dialogs and clipmon-mode
Date: Sun, 27 Dec 2015 01:29:07 -0600 [thread overview]
Message-ID: <CA+XjW6xBWHO3aW5Nb8e5CZf43tqxNSMsVAcJk=8_0axs3G-7pg@mail.gmail.com> (raw)
In-Reply-To: <83a8ozom2y.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]
It looks like the gui menu runs through timer_check to check for any emacs
timers, and when the clipmon timer is triggered, it checks the x selection,
which also runs through timer_check. Putting the clipmon timer through that
routine twice might be throwing things off - it seems like it's the second
pass which get stuck in an endless loop.
I'm not positive about that though - I'm still learning my way around the
system and gdb. I'll keep tracing through it - I've been wanted to learn
more about Emacs internals so I could work on them someday, and this looks
like as good a place as any to start...
Brian
On Thu, Dec 24, 2015 at 10:20 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Brian Burns <bburns.km@gmail.com>
> > Date: Thu, 24 Dec 2015 01:43:39 -0600
> > Cc: Eli Zaretskii <eliz@gnu.org>, 22214@debbugs.gnu.org
> >
> > I looked at some of the internals - as Eli said there's an event loop
> for the x
> > dialog that also checks the existing Emacs timers, which in this case
> would be
> > checking the x selection and starting another timer.
>
> What I don't understand is how menus enter the picture, since the
> lockup doesn't happen unless a menu is open.
>
> Understanding that might be an important step towards finding a
> solution.
>
[-- Attachment #2: Type: text/html, Size: 1826 bytes --]
next prev parent reply other threads:[~2015-12-27 7:29 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-20 6:26 bug#22214: 25.0.50; lock up with gui dialogs and clipmon-mode Joseph Mingrone
2015-12-20 15:54 ` Eli Zaretskii
2015-12-21 2:31 ` Joseph Mingrone
2015-12-21 15:24 ` Eli Zaretskii
2015-12-21 16:41 ` Joseph Mingrone
2015-12-21 17:50 ` Eli Zaretskii
2015-12-21 19:42 ` Joseph Mingrone
2015-12-21 0:21 ` Brian Burns
2015-12-21 0:45 ` Joseph Mingrone
2015-12-22 7:56 ` Brian Burns
2015-12-21 15:26 ` Eli Zaretskii
2015-12-22 5:21 ` Joseph Mingrone
2015-12-22 16:06 ` Eli Zaretskii
2015-12-23 17:00 ` Joseph Mingrone
2015-12-23 17:12 ` Eli Zaretskii
2015-12-23 18:18 ` Joseph Mingrone
2015-12-23 18:22 ` Eli Zaretskii
2015-12-23 20:16 ` Brian Burns
2015-12-23 21:21 ` Joseph Mingrone
2015-12-24 7:43 ` Brian Burns
2015-12-24 16:20 ` Eli Zaretskii
2015-12-27 7:29 ` Brian Burns [this message]
2022-04-23 14:06 ` Lars Ingebrigtsen
2022-04-24 13:23 ` Joseph Mingrone
2022-04-25 0:50 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-23 8:02 ` Lars Ingebrigtsen
2022-05-23 19:02 ` Joseph Mingrone
2022-05-24 0:27 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-29 15:51 ` Joseph Mingrone
2022-05-29 23:58 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-30 6:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-30 13:00 ` Joseph Mingrone
2022-05-30 13:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+XjW6xBWHO3aW5Nb8e5CZf43tqxNSMsVAcJk=8_0axs3G-7pg@mail.gmail.com' \
--to=bburns.km@gmail.com \
--cc=22214@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jrm@ftfl.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).