From: thamesynne <thamesynne@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Intermittent bug in Firefox 88+ on x64/musl
Date: Thu, 22 Jul 2021 22:14:29 +0200 [thread overview]
Message-ID: <20210722201429.oVjdL72bIZScBGXhzVKvv6d0TmTp4nmFdGqSaJNTC0Q@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31933@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 796 bytes --]
New comment by thamesynne on void-packages repository
https://github.com/void-linux/void-packages/issues/31933#issuecomment-885202857
Comment:
First, i do a `ps ax | grep fire`; that gives me a list of candidates. Usually there are just two with the command line 'firefox' (without any options), and between them are lots of subprocesses with very long command lines full of options. Mostly it's the one with the higher PID that needs killing - unless there are no subprocesses between those two; then the PIDs have wrapped and the lower one needs to be killed.
I think that heuristic has only steered me wrong once, and I was in a hurry that time.
(Having said which, I've only used the 32-bt glibc version since I created this bug report, and that doesn't exhibit the problem at all.)
next prev parent reply other threads:[~2021-07-22 20:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 2:28 [ISSUE] " thamesynne
2021-07-13 13:30 ` ericonr
2021-07-22 19:16 ` dkwo
2021-07-22 19:21 ` dkwo
2021-07-22 20:14 ` thamesynne [this message]
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=20210722201429.oVjdL72bIZScBGXhzVKvv6d0TmTp4nmFdGqSaJNTC0Q@z \
--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).