From: thamesynne <thamesynne@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Intermittent bug in Firefox 88+ on x64/musl
Date: Tue, 13 Jul 2021 04:28:25 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31933@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1527 bytes --]
New issue by thamesynne on void-packages repository
https://github.com/void-linux/void-packages/issues/31933
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname: Void 5.11.22_1 x86_64-musl GenuineIntel notuptodate rFF
* package: firefox-89.0.2_1 (but has been observed since at least Firefox 88)
* X server: Xvnc provided by tigervnc-1.10.1_3
### Expected behavior
Not the actual behaviour...
### Actual behavior
When right clicking to bring up a context menu, or dropping down a selection box, occasionally Firefox will spawn a new process, which doesn't do anything useful but does block at least Firefox, and sometimes the entire X server. Manually killing this process unfreezes everything, allowing the session to continue.
No error output appears from Firefox to suggest what's gone wrong.
Other than the fact that it results from Firefox dropping down a menu, I can see no pattern to why it occurs. Sometimes it happens with every 3rd or 4th right click, sometimes an entire session will pass without it happening.
I have greated a 32-bit glibc chroot and tested Firefox-i686 in that environment; the bug does not seem present there. Has Firefox grown an incompatibility with musl?
### Steps to reproduce the behavior
Bug is intermittent - see above.
(I apologise for not being able to provide more detail.)
next reply other threads:[~2021-07-13 2:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 2:28 thamesynne [this message]
2021-07-13 13:30 ` ericonr
2021-07-22 19:16 ` dkwo
2021-07-22 19:21 ` dkwo
2021-07-22 20:14 ` thamesynne
2021-07-22 20:15 ` thamesynne
2021-07-23 8:59 ` dkwo
2022-05-25 2:15 ` github-actions
2022-06-09 2:11 ` [ISSUE] [CLOSED] " github-actions
2023-04-08 8:31 ` vincele
2023-04-08 8:35 ` vincele
2023-04-08 8:39 ` vincele
2023-04-08 8:41 ` vincele
2023-04-08 13:31 ` dkwo
2023-04-08 14:14 ` vincele
2023-04-08 17:41 ` vincele
2023-04-08 18:02 ` snark-attack
2023-04-09 8:02 ` vincele
2023-08-09 21:05 ` casualtyface
2023-08-09 22:11 ` vincele
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31933@inbox.vuxu.org \
--to=thamesynne@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
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 NNTP newsgroup(s).