From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Justin Madru <jdm64@gawab.com>
Cc: lkml <linux-kernel@vger.kernel.org>, John Stoffel <john@stoffel.org>
Subject: Re: 2.6.29-rc1 Firefox crashing on page load
Date: Sat, 17 Jan 2009 01:10:54 -0800 [thread overview]
Message-ID: <4971A09E.1050503@gmail.com> (raw)
In-Reply-To: <49719B53.8050300@gawab.com>
Justin Madru wrote:
> Justin P. Mattock wrote:
>> I'm not seeing this with firefox over here.
>> The setup I have is the latest beta,
>> located in /usr/lib/firefox/ with a soft link to /usr/bin/
>> I don't have gnome2 vfs installed though.
>> just a bare firefox with 2 plugins(flash,null)
>> located in /.mozilla/plugins/
>> for restorecon.
>>
>> not sure what distro you have, but with ubuntu
>> I noticed a quit a bit of other links created.
>> that is installing through apt-get, rather
>> just downloading the source and putting it wherever.
>>
>> regards;
>>
>> Justin P. Mattock
>>
> I'm running ubuntu 8.10, with 2 custom kernels 2.6.28 and 2.6.29-rc2.
>
> I've done a little bit more testing. This time with 4 version of
> firefox (3.0.5-ubuntu, 3.0.4, 3.1.b2, 3.2.a1) straight from
> mozilla.org, except the ubuntu one.
> What I found is that all versions crash when loading iGoogle, sofar
> the only site that makes it crash, except 3.2a1.
> Since iGoogle is my hompage, they all crash once loading is done
> (except 3.2a1), unless I'm fast enough and load a different page.
> But, _every_ version crashes if I go to Preferences->Main or
> Preferences->Applications.
>
> None of this crashing happens if I'm booted into a .28 kernel, only on
> a .29-rc kernel.
> Henceforth, I still think it's a kernel regression, but one that's
> going to be almost impossible to debug!
> I've hit the most narrow minded bug on the planet! Very sad....
> Seems like I always hit the undebugable regressions that nobody else
> sees ;-(
>
> Justin Madru
>
what happens when you download the source?
then once unpacked issue ./firefox
just to see what happens without any plugins/apps.
over here I have the beta no apps
basically as light as possible just flash
(since all web sites use that.)
I did have a crash though,
but was due to me not allowing
an allow rule for SELinux(too lazy at the moment);
but besides any allow rules I'm not having any issues.
(knock on wood).
you can also try renaming gnome2 gconf and
.mozilla just to see
regards;
Justin P. Mattock
next prev parent reply other threads:[~2009-01-17 9:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 20:56 Justin Madru
2009-01-17 2:28 ` Justin Madru
2009-01-17 3:27 ` John Stoffel
2009-01-17 3:27 ` Justin P. Mattock
2009-01-17 8:48 ` Justin Madru
2009-01-17 9:10 ` Justin P. Mattock [this message]
2009-01-17 20:21 ` Jesper Juhl
2009-01-17 21:07 ` Justin Madru
2009-01-17 22:51 ` Justin P. Mattock
2009-01-18 0:05 ` Justin Madru
2009-01-18 0:46 ` Justin P. Mattock
2009-01-18 2:06 ` Justin Madru
2009-01-18 2:49 ` Justin P. Mattock
2009-01-20 0:32 ` [bisected] " Justin Madru
2009-01-20 1:06 ` Justin P. Mattock
2009-01-20 1:25 ` Hiroshi Shimamoto
2009-01-20 6:19 ` Justin Madru
2009-01-20 18:28 ` Hiroshi Shimamoto
2009-01-20 19:22 ` Justin Madru
2009-01-20 19:48 ` Hiroshi Shimamoto
2009-01-21 2:39 ` Justin Madru
2009-01-21 3:04 ` Hiroshi Shimamoto
2009-01-20 1:39 ` Peter Annema
2009-01-20 7:15 ` Heiko Carstens
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=4971A09E.1050503@gmail.com \
--to=justinmattock@gmail.com \
--cc=jdm64@gawab.com \
--cc=john@stoffel.org \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome