all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: nightowl <nightowl@members.fsf.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: GNU Icecat crashed tab
Date: Wed, 26 Sep 2018 04:38:33 +0200	[thread overview]
Message-ID: <109421fc356f21fbed0adb92d39723e9@posteo.net> (raw)
In-Reply-To: <874lefhsz2.fsf@elephly.net>

I am running GuixSD on a 2008 model Dell Inspiron with I believe to be 
an Intel T5300 core 2 CPU.  I have only just started using GuixSD for 
less than a year now, and still on the learning curve.  So, do you think 
the tab crash I see with Icecat could be related to the hardware on my 
PC?

On 24.09.2018 16:26, Ricardo Wurmus wrote:
> Ricardo Wurmus <rekado@elephly.net> writes:
> 
>> Andreas Enge <andreas@enge.fr> writes:
>> 
>>> On Sat, Sep 22, 2018 at 12:14:30PM +0200, Ricardo Wurmus wrote:
>>>> I have seen similar behaviour on a Thinkpad T60 with an x86_64 CPU
>>>> (upgraded from the i686 CPU that it came with).  Icecat tabs crash 
>>>> and
>>>> it can be avoided only by disabling all extensions.
>>>> 
>>>> I don’t know what the cause is.
>>> 
>>> This is weird. I have not experienced it, and I just tried to load 
>>> the
>>> homedepot.com website, which does not pose any problem.
>> 
>> I don’t see this on other x86_64 machines; among those computers that 
>> I
>> have access to, only the T60 is affected, which is why I thought it
>> might simply be a hardware problem.
>> 
>>> Could it be related to memory consumption and, for instance, the 
>>> number
>>> of open tabs?
>> 
>> No, this happens with just one tab.  I found that I couldn’t get it to
>> crash with a simply static website like https://elephly.net, but it
>> would crash somewhat reliably with sites that embed media.
> 
> There’s a bug report about crashes on i686:
> https://issues.guix.info/issue/29736
> 
> FWIW this is the same T60, just before the upgrade to an x86_64 CPU.
> Nothing else on that laptop has been changed since that bug report.
> 
> --
> Ricardo

  reply	other threads:[~2018-09-26  2:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-22  2:09 GNU Icecat crashed tab nightowl
2018-09-22 10:14 ` Ricardo Wurmus
2018-09-22 10:30   ` Andreas Enge
2018-09-22 10:56     ` Ricardo Wurmus
2018-09-24 14:26       ` Ricardo Wurmus
2018-09-26  2:38         ` nightowl [this message]
2018-09-26  5:03           ` Mike Gerwitz
2018-09-27  1:36             ` nightowl
2018-09-27  2:26               ` Mike Gerwitz
2018-09-27  3:30                 ` nightowl
2018-09-27  6:06                   ` Björn Höfling
2018-09-29  3:26                     ` nightowl
2018-09-29  8:14                       ` Ricardo Wurmus
2018-09-30  2:27                         ` nightowl
2018-09-30 15:20                           ` Mike Gerwitz
2018-09-30 23:50                             ` nightowl

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=109421fc356f21fbed0adb92d39723e9@posteo.net \
    --to=nightowl@members.fsf.org \
    --cc=help-guix@gnu.org \
    --cc=rekado@elephly.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.