From: thamesynne <thamesynne@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: firefox i686 segfaults on startup
Date: Fri, 30 Sep 2022 15:15:38 +0200 [thread overview]
Message-ID: <20220930131538._7SWoYXKIac70m20_pWQFiR2-vBZ7-XFFBR-q_Q-7gI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39538@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 890 bytes --]
New comment by thamesynne on void-packages repository
https://github.com/void-linux/void-packages/issues/39538#issuecomment-1263561823
Comment:
You've clearly never tried using 64-bit Firefox on a system booting from a USB key, with 4GB RAM.
I have, which is why I don't do that any more. It reliably freezes up whichever machine I try it on; Firefox claims 28GB space for itself, which is all very well until it decides it's going to try and use it all.
32-bit Firefox, for obvious reasons, doesn't do that. So even on my 64-bit systems, I run 32-bit Firefox in a chroot.
Now, rather than telling me how I've spent the last three decades using my machines all wrong, how about you *actually try fixing the bug I have reported*? Or if you have no interest in doing that, how about simply keeping your own counsel and not doing your level best to reduce the Void userbase by one?
next prev parent reply other threads:[~2022-09-30 13:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 9:13 [ISSUE] " thamesynne
2022-09-30 9:35 ` thamesynne
2022-09-30 11:12 ` Duncaen
2022-09-30 11:25 ` thamesynne
2022-09-30 11:27 ` thamesynne
2022-09-30 11:37 ` q66
2022-09-30 12:19 ` thamesynne
2022-09-30 12:28 ` thamesynne
2022-09-30 13:03 ` q66
2022-09-30 13:15 ` thamesynne [this message]
2022-09-30 13:20 ` thamesynne
2022-09-30 13:44 ` q66
2022-09-30 13:59 ` thamesynne
2022-09-30 14:08 ` paper42
2022-09-30 14:29 ` q66
2022-09-30 15:15 ` mtboehlke
2022-09-30 15:16 ` q66
2022-09-30 15:17 ` q66
2022-09-30 15:57 ` mtboehlke
2022-09-30 21:36 ` [ISSUE] [CLOSED] " Duncaen
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=20220930131538._7SWoYXKIac70m20_pWQFiR2-vBZ7-XFFBR-q_Q-7gI@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).