public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jeremi Piotrowski <jeremi.piotrowski@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Firefox 45.2.0 segfaulting
Date: Sat, 16 Jul 2016 17:33:11 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.20.1607161727430.15353@gentoo-tp> (raw)
In-Reply-To: <nm8plp$rkd$1@ger.gmane.org>

On Thu, 14 Jul 2016, Grant Edwards wrote:
> 
> Same behavior with 47.0.1.  Starting 47 in "safe mode" avoids the
> problem, but starting 47 in normal mode with all extensions disabled
> still crashes.
> 
> I downgraded to 38.8, and everyting works fine again.
> 

Are you running all of these test with the build-from-source 
www-client/firefox ebuild? I used to do that but after not being able to 
track down the cause of some weird font-related graphics glitches, I 
settled for the binary www-client/firefox-bin package and haven't had 
problems since. I always run ~amd64 firefox-bin, currently at 47 and have 
no problems whatsoever.

Definitely recommend you try that before going for chrome.


  parent reply	other threads:[~2016-07-16 15:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-14 17:55 [gentoo-user] Firefox 45.2.0 segfaulting Grant Edwards
2016-07-14 19:11 ` Alexander Kapshuk
2016-07-14 19:37 ` [gentoo-user] " Grant Edwards
2016-07-15 15:55   ` Ian Zimmerman
2016-07-15 22:42     ` Neil Bothwick
2016-07-16 15:33   ` Jeremi Piotrowski [this message]
2016-07-18 14:27     ` Grant Edwards
2016-07-17  3:58   ` Ian Zimmerman
2016-07-18 14:29     ` Grant Edwards
2016-08-05 13:21   ` Grant Edwards
2016-09-24 20:03     ` Grant Edwards
2016-07-15 16:44 ` [gentoo-user] " Adrien Sohier
2016-07-16 14:56 ` lukash
2016-09-25 14:24 ` [gentoo-user] " Kai Krakow

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=alpine.LNX.2.20.1607161727430.15353@gentoo-tp \
    --to=jeremi.piotrowski@gmail.com \
    --cc=gentoo-user@lists.gentoo.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