Ubuntu
firefox package

Firefox > 44 is broken on all big-endian architectures

Bug #1583849 reported by Fritz Hudnut
48
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Mozilla Firefox
Confirmed
Unknown
firefox (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

OK, the reason I'm posting back here, running Lu 16.04 on an PPC iBook, and MATE/XFCE 16.04 on a PM ST. . . did a dist-upgrade today, so it now running the new "22" kernel and saw in the list of upgrades new updates to FF and T-bird . . . on both machines after reboot FF window frame loads . . . and then crashes . . . no data is ever filled into the browser window.

The iBook error says it "doesn't have enough memory to report the problem" . . . and on the PM . . . apparently it says the error report was "corrupted" . . . no launchpad window opened in the browser when I clicked on the "report the problem."

Tried to revert to the old kernel in the iBook several times, seemingly failed to boot the old one . . . shut it down.

I went to the PM running 16.04 U-MATE and tried the same dist-upgrade via console there, that upgrade was much larger than the Lu system, but subsequently FF also then failed to launch w/o crashing . . . installed Midori to make an apple user post, but when I tried to start a new thread there Midori crashed as well.

I ran "apt-get -f install" in both the iBook & the PM . . . nothing showed up. No "comment" in the terminal during the upgrade asking any questions or reporting "problems" . . . but FF is kaput!!!!

I'm back in OSX 10.5 side until things cool down for the browsers in 16.04 PPC Lu & U-MATE/XFCE.

e...

Revision history for this message
In , Martin Husemann (ub71a5bwcb7k-6kfa0n-b69y0hv8hgzd) wrote :
Download full text (6.0 KiB)

Probably same or similar underlying issue as bug 986328, I see flashing display and lots of "crash reporter logs":

Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 0 (t=4.86961)|[25246][GFX1]: Unknown image format 0 (t=904.76)|[25242][GFX1]:

coming from:

#6 mozilla::gfx::GfxFormatToCairoFormat (format=format@entry=mozilla::gfx::SurfaceFormat::B8G8R8A8)
    at /usr/pkgobj/www/firefox/work/firefox-46.0/gfx/2d/HelpersCairo.h:163
#7 0xfffffffff3751e84 in GfxFormatToCairoFormat (format=mozilla::gfx::SurfaceFormat::B8G8R8A8)
    at /usr/pkgobj/www/firefox/work/firefox-46.0/gfx/2d/HelpersCairo.h:152
#8 mozilla::gfx::CreateSubImageForData (aData=<optimized out>, aRect=..., aStride=<optimized out>, aFormat=<optimized out>)
    at /usr/pkgobj/www/firefox/work/firefox-46.0/gfx/2d/DrawTargetCairo.cpp:283
#9 0xfffffffff37521fc in mozilla::gfx::GetCairoSurfaceForSourceSurface (aSurface=<optimized out>, aExistingOnly=aExistingOnly@entry=false,
    aSubImage=...) at /usr/pkgobj/www/firefox/work/firefox-46.0/gfx/2d/DrawTargetCairo.cpp:384
#10 0xfffffffff3752684 in mozilla::gfx::GfxPatternToCairoPattern (aPattern=..., aAlpha=<optimized out>, aTransform=...)
    at /usr/pkgobj/www/firefox/work/firefox-46.0/gfx/2d/DrawTargetCairo.cpp:507
#11 0xfffffffff3752efc in mozilla::gfx::DrawTargetCairo::DrawPattern (this=this@entry=0xffffffffdc662520, aPattern=..., aStrokeOptions=...,
    aOptions=..., aDrawType=aDrawType@entry=mozilla::gfx::DrawTargetCairo::DRAW_FILL, aPathBoundsClip=<optimized out>)
    at /usr/pkgobj/www/firefox/work/firefox-46.0/gfx/2d/DrawTargetCairo.cpp:961
#12 0xfffffffff3754d74 in mozilla::gfx::DrawTargetCairo::FillRect (this=0xffffffffdc662520, aRect=..., aPattern=..., aOptions=...)
    at /usr/pkgobj/www/firefox/work/firefox-46.0/gfx/2d/DrawTargetCairo.cpp:1057
#13 0xfffffffff387c000 in gfxSurfaceDrawable::DrawInternal (this=this@entry=0xffffffffdda47100, aDrawTarget=aDrawTarget@entry=0xffffffffdc662520,
    aOp=aOp@entry=mozilla::gfx::CompositionOp::OP_OVER, aAntialiasMode=<optimized out>, aFillRect=..., aSamplingRect=..., aExtendMode=<optimized out>,
    aFilter=<optimized out>, aOpacity=<optimized out>, aTransform=...) at /usr/pkgobj/www/firefox/work/firefox-46.0/gfx/thebes/gfxDrawable.cpp:106
#14 0xfffffffff387c23c in gfxSurfaceDrawable::Draw (this=this@entry=0xffffffffdda47100, aContext=aContext@entry=0xffffffffdc776e80, aFillRect=...,
    aExtendMode=aExtendMode@entry=mozilla::gfx::ExtendMode::CLAMP, aFilter=@0xffffffffffff81a8: mozilla::gfx::Filter::GOOD, aOpacity=<optimized out>,
    aTransform=...) at /usr/pkgobj/www/firefox/work/firefox-46.0/gfx/thebes/gfxDrawable.cpp:77
#15 0xfffffffff38da684 in gfxUtils::DrawPixelSnapped (aContext=aContext@entry=0xffffffffdc776e80, aDrawable=<optimized out>, aImageSize=...,
    aRegion=..., aFormat=<optimized out>, aFilter=aFilter@entry=mozilla::gfx::Filter::GOOD, aImageFlags=<optimized out>, aOpacity=1)
    at /usr/pkgobj/www/firefox/work/firefox-46.0/gfx/thebes/gfxUtils.cpp:694
#16 0xfffffffff3910c7c in mozilla::image::imgFrame::Draw (this=0xffffffffe6f36480, aContext=aContext@entry=0xffffffffdc776e80, aRegion=...,
    aFilter=aFilter@entry=mozilla::gfx::Fil...

Read more...

Revision history for this message
In , Martin Husemann (ub71a5bwcb7k-6kfa0n-b69y0hv8hgzd) wrote :

Note that with commmenting out the gfxCriticalError() in this function and in the next, like:

static inline cairo_content_t
GfxFormatToCairoContent(SurfaceFormat format)
{
  switch (format)
  {
    case SurfaceFormat::A8R8G8B8_UINT32:
      return CAIRO_CONTENT_COLOR_ALPHA;
    case SurfaceFormat::X8R8G8B8_UINT32:
    case SurfaceFormat::R5G6B5_UINT16: //fall through
      return CAIRO_CONTENT_COLOR;
    case SurfaceFormat::A8:
      return CAIRO_CONTENT_ALPHA;
    default:
// gfxCriticalError() << "Unknown image content format " << (int)format;
      return CAIRO_CONTENT_COLOR_ALPHA;
  }
}

makes it mostly work, only a full clienat area black flash every now and then

Revision history for this message
In , Milaninbugzilla (milaninbugzilla) wrote :

If you want to "ifdef big endian" these errors, we'll probably take a patch, but it may be better to figure out what the underlying problem is.

Revision history for this message
In , Martin Husemann (ub71a5bwcb7k-6kfa0n-b69y0hv8hgzd) wrote :

No, I don't want to remove the errors - just noting that it mostly works.

I currently have no idea where to start looking what goes wrong. This also is a relatively recent regression, not sure about 45, but 44 certainly did work well for me.

It only seems to happen for images, something goes wrong during composition and a full redraw of the layers tree is triggered to fix it? The visual result in the end is fine.

Revision history for this message
In , Lsalzman (lsalzman) wrote :

Created attachment 8749234
handle big-endian formats in Cairo format conversions

This is an unfortunately necessary hack until we resolve the overall issue of inconsistent usage of B8G8R8A8 throughout the tree. It's better than crashing, at least.

Revision history for this message
In , Jmuizelaar (jmuizelaar) wrote :

Comment on attachment 8749234
handle big-endian formats in Cairo format conversions

Review of attachment 8749234:
-----------------------------------------------------------------

Do you know where the wrong formats are coming from?

Revision history for this message
In , Jmuizelaar (jmuizelaar) wrote :

It looks like they're coming from ImageLib. Can we try fixing those instead in bug 1270942

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1583849/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
John Paul Adrian Glaubitz (glaubitz)
affects: ubuntu → firefox (Ubuntu)
Bug Watch Updater (bug-watch-updater)
Changed in firefox:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
John Paul Adrian Glaubitz (glaubitz) wrote :

As you can see in the linked upstream bug report, Firefox is currently broken on all big-endian architectures. The only known workaround for this is currently downgrading to Firefox 44.

Adrian

Revision history for this message
Fritz Hudnut (este-el-paz) wrote : Re: [Bug 1583849] Re: dist-upgrade & FF upgrade breaks FF & Midori 16.04 PPC

@John:

Thanks for the follow-up . . . appreciate the suggestion on downgrading;
however it seemed that there was some problem with Midori as well . . .
??? Not a whole lot of options for browsers in PPC . . . hopefully FF will
pull itself together.

F

On Fri, May 20, 2016 at 6:20 AM, John Paul Adrian Glaubitz <
<email address hidden>> wrote:

> As you can see in the linked upstream bug report, Firefox is currently
> broken on all big-endian architectures. The only known workaround for
> this is currently downgrading to Firefox 44.
>
> Adrian
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1583849
>
> Title:
> dist-upgrade & FF upgrade breaks FF & Midori 16.04 PPC
>
> Status in Mozilla Firefox:
> Confirmed
> Status in firefox package in Ubuntu:
> New
>
> Bug description:
> OK, the reason I'm posting back here, running Lu 16.04 on an PPC
> iBook, and MATE/XFCE 16.04 on a PM ST. . . did a dist-upgrade today,
> so it now running the new "22" kernel and saw in the list of upgrades
> new updates to FF and T-bird . . . on both machines after reboot FF
> window frame loads . . . and then crashes . . . no data is ever filled
> into the browser window.
>
> The iBook error says it "doesn't have enough memory to report the
> problem" . . . and on the PM . . . apparently it says the error report
> was "corrupted" . . . no launchpad window opened in the browser when I
> clicked on the "report the problem."
>
> Tried to revert to the old kernel in the iBook several times,
> seemingly failed to boot the old one . . . shut it down.
>
> I went to the PM running 16.04 U-MATE and tried the same dist-upgrade
> via console there, that upgrade was much larger than the Lu system,
> but subsequently FF also then failed to launch w/o crashing . . .
> installed Midori to make an apple user post, but when I tried to start
> a new thread there Midori crashed as well.
>
> I ran "apt-get -f install" in both the iBook & the PM . . . nothing
> showed up. No "comment" in the terminal during the upgrade asking any
> questions or reporting "problems" . . . but FF is kaput!!!!
>
> I'm back in OSX 10.5 side until things cool down for the browsers in
> 16.04 PPC Lu & U-MATE/XFCE.
>
> e...
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/firefox/+bug/1583849/+subscriptions
>

Revision history for this message
Launchpad Janitor (janitor) wrote : Re: dist-upgrade & FF upgrade breaks FF & Midori 16.04 PPC

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in firefox (Ubuntu):
status: New → Confirmed
Revision history for this message
elvisplatini (regis-etourmy) wrote :

Hi,
On my powermac G5, running Lubuntu 16.04, I downgraded firefox to 45.02, and it worked again (I'm currently using it). I used:

sudo apt-get install firefox=45.0.2+build1-0ubuntu1
sudo apt-mark hold firefox

I know it's not really satisfactory, that it would be better to try to fix the 46 version bug, but until I manage to succeed in this skill (maybe in 150 years), it allows me to avoid going back to macOS 10.5.

Revision history for this message
Fritz Hudnut (este-el-paz) wrote :

@elvisplatini:

Thanks for the post, I was hoping that since this issue is "significant" . . . that it would have been patched by now . . . but apparently not. I did try to look in synaptic to see if the history of FF versions would be listed, but, nope . . . only the 46 . . . . In 16.04 I have been using Qupzilla, it's OK, but function is a bit "limited" and/or even "slow" . . . like trying to log into LP here the cursor wouldn't load into the email user box . . . for several minutes . . . then, I went back to it, and it was there . . . .

I might get around to trying out your commands . . . but, if it is marked as "hold" . . . if and when the patched version shows up (hard to know when that might happen) . . . how would I "un-hold" it?

F

Revision history for this message
ernsteiswuerfel (erhard-f) wrote :

Firefox 47 works again.

Revision history for this message
Fritz Hudnut (este-el-paz) wrote : Re: [Bug 1583849] Re: dist-upgrade & FF upgrade breaks FF & Midori 16.04 PPC

yep. Have so many bug reports out on stuff, didn't remember to post here
about it . . . .

On Sat, Jun 18, 2016 at 3:57 PM, ernsteiswuerfel <email address hidden>
wrote:

> Firefox 47 works again.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1583849
>
> Title:
> dist-upgrade & FF upgrade breaks FF & Midori 16.04 PPC
>
> Status in Mozilla Firefox:
> Confirmed
> Status in firefox package in Ubuntu:
> Confirmed
>
> Bug description:
> OK, the reason I'm posting back here, running Lu 16.04 on an PPC
> iBook, and MATE/XFCE 16.04 on a PM ST. . . did a dist-upgrade today,
> so it now running the new "22" kernel and saw in the list of upgrades
> new updates to FF and T-bird . . . on both machines after reboot FF
> window frame loads . . . and then crashes . . . no data is ever filled
> into the browser window.
>
> The iBook error says it "doesn't have enough memory to report the
> problem" . . . and on the PM . . . apparently it says the error report
> was "corrupted" . . . no launchpad window opened in the browser when I
> clicked on the "report the problem."
>
> Tried to revert to the old kernel in the iBook several times,
> seemingly failed to boot the old one . . . shut it down.
>
> I went to the PM running 16.04 U-MATE and tried the same dist-upgrade
> via console there, that upgrade was much larger than the Lu system,
> but subsequently FF also then failed to launch w/o crashing . . .
> installed Midori to make an apple user post, but when I tried to start
> a new thread there Midori crashed as well.
>
> I ran "apt-get -f install" in both the iBook & the PM . . . nothing
> showed up. No "comment" in the terminal during the upgrade asking any
> questions or reporting "problems" . . . but FF is kaput!!!!
>
> I'm back in OSX 10.5 side until things cool down for the browsers in
> 16.04 PPC Lu & U-MATE/XFCE.
>
> e...
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/firefox/+bug/1583849/+subscriptions
>

Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote : Re: dist-upgrade & FF upgrade breaks FF & Midori 16.04 PPC

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1583849

tags: added: iso-testing
Martin Wimpress  (flexiondotorg)
summary: - dist-upgrade & FF upgrade breaks FF & Midori 16.04 PPC
+ Firefox crashes on PowerPC
summary: - Firefox crashes on PowerPC
+ Firefox > 44 is broken on all big-endian architectures
Revision history for this message
ernsteiswuerfel (erhard-f) wrote :

No longer an issue since Firefox is no longer on Yakkety's daily iso?

Revision history for this message
K1773R (k1773r) wrote :

yes this still is an issue!

Revision history for this message
K1773R (k1773r) wrote :

btw, this bug should be extended. firefox 48 and firefox 49 cant be build on big endian systems too, their internal toolchain is broken. see the builder logs

Revision history for this message
ernsteiswuerfel (erhard-f) wrote :

@K1773R:
What I was trying to point out is, that Firefox is not part of the daily iso of Ubuntu MATE 16.10 of today (12.10.2016). An error or is it gone for sure?

Unlike yesterdays Xenial daily iso where Firefox 47 lives quite happily and works fine.

Bug Watch Updater (bug-watch-updater)
Changed in firefox:
status: Confirmed → Fix Released
Revision history for this message
ernsteiswuerfel (erhard-f) wrote :

Nice to see that bug fixed upstream! Will there be new PPC-builds of Firefox? ATM there are none in the repository...

Revision history for this message
Herminio (herminio-hernandezjr) wrote : Re: [Bug 1583849] Re: Firefox > 44 is broken on all big-endian architectures

On Monday, December 12, 2016 4:21:38 AM MST you wrote:
> Nice to see that bug fixed upstream! Will there be new PPC-builds of
> Firefox? ATM there are none in the repository...
 It would be nice!

Herminio

Revision history for this message
Fritz Hudnut (este-el-paz) wrote :

I just updated/graded my PPC units yesterday, didn't look too closely over
the whole list, it was large, 60 packages plus a kernel. Obviously since
this bug was posted FF was repaired, but, we know that the various ubuntu
distros are phasing PPC out . . . the browser is what needs the most
maintenance.

Don't know if it's possible to find a distro that is going to continue to
support PPC and get the FF package from there?? Most everybody uses
Debian, but the plan is for them to drop PPC as well. Personally my PPC
computers are RAM challenged, as well as cpu challenged and my use is
intermittent; I spent a few minutes checking another distro a couple days
ago, but the "server was down" for downloads . . . after several tries I
moved on.

If I get a moment to boot my PPC computer I'll try to check what version of
FF I have; I definitely launched FF in both of them yesterday, and . . . it
worked, so did Qupzilla . . . .

F

On Sun, Dec 11, 2016 at 8:21 PM, ernsteiswuerfel <email address hidden>
wrote:

> Nice to see that bug fixed upstream! Will there be new PPC-builds of
> Firefox? ATM there are none in the repository...
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1583849
>
> Title:
> Firefox > 44 is broken on all big-endian architectures
>
> Status in Mozilla Firefox:
> Fix Released
> Status in firefox package in Ubuntu:
> Confirmed
>
> Bug description:
> OK, the reason I'm posting back here, running Lu 16.04 on an PPC
> iBook, and MATE/XFCE 16.04 on a PM ST. . . did a dist-upgrade today,
> so it now running the new "22" kernel and saw in the list of upgrades
> new updates to FF and T-bird . . . on both machines after reboot FF
> window frame loads . . . and then crashes . . . no data is ever filled
> into the browser window.
>
> The iBook error says it "doesn't have enough memory to report the
> problem" . . . and on the PM . . . apparently it says the error report
> was "corrupted" . . . no launchpad window opened in the browser when I
> clicked on the "report the problem."
>
> Tried to revert to the old kernel in the iBook several times,
> seemingly failed to boot the old one . . . shut it down.
>
> I went to the PM running 16.04 U-MATE and tried the same dist-upgrade
> via console there, that upgrade was much larger than the Lu system,
> but subsequently FF also then failed to launch w/o crashing . . .
> installed Midori to make an apple user post, but when I tried to start
> a new thread there Midori crashed as well.
>
> I ran "apt-get -f install" in both the iBook & the PM . . . nothing
> showed up. No "comment" in the terminal during the upgrade asking any
> questions or reporting "problems" . . . but FF is kaput!!!!
>
> I'm back in OSX 10.5 side until things cool down for the browsers in
> 16.04 PPC Lu & U-MATE/XFCE.
>
> e...
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/firefox/+bug/1583849/+subscriptions
>

Revision history for this message
Fritz Hudnut (este-el-paz) wrote :

Just checked my iBook/Lu 16.04, and Powermac/U-MATE 16.04, both have FF
47.0+build3-Oubur "installed" and shown as "latest version" . . . in my
MacPro/10.9 I have FF 50.0.2 "up to date." Usually PPC is a couple
versions back, so, it looks like a tad bit more than that . . . it's fading
awaaaaaayyyyyy . . . .

F

On Sun, Dec 11, 2016 at 9:02 PM, Herminio <email address hidden>
wrote:

> On Monday, December 12, 2016 4:21:38 AM MST you wrote:
> > Nice to see that bug fixed upstream! Will there be new PPC-builds of
> > Firefox? ATM there are none in the repository...
> It would be nice!
>
> Herminio
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1583849
>
> Title:
> Firefox > 44 is broken on all big-endian architectures
>
> Status in Mozilla Firefox:
> Fix Released
> Status in firefox package in Ubuntu:
> Confirmed
>
> Bug description:
> OK, the reason I'm posting back here, running Lu 16.04 on an PPC
> iBook, and MATE/XFCE 16.04 on a PM ST. . . did a dist-upgrade today,
> so it now running the new "22" kernel and saw in the list of upgrades
> new updates to FF and T-bird . . . on both machines after reboot FF
> window frame loads . . . and then crashes . . . no data is ever filled
> into the browser window.
>
> The iBook error says it "doesn't have enough memory to report the
> problem" . . . and on the PM . . . apparently it says the error report
> was "corrupted" . . . no launchpad window opened in the browser when I
> clicked on the "report the problem."
>
> Tried to revert to the old kernel in the iBook several times,
> seemingly failed to boot the old one . . . shut it down.
>
> I went to the PM running 16.04 U-MATE and tried the same dist-upgrade
> via console there, that upgrade was much larger than the Lu system,
> but subsequently FF also then failed to launch w/o crashing . . .
> installed Midori to make an apple user post, but when I tried to start
> a new thread there Midori crashed as well.
>
> I ran "apt-get -f install" in both the iBook & the PM . . . nothing
> showed up. No "comment" in the terminal during the upgrade asking any
> questions or reporting "problems" . . . but FF is kaput!!!!
>
> I'm back in OSX 10.5 side until things cool down for the browsers in
> 16.04 PPC Lu & U-MATE/XFCE.
>
> e...
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/firefox/+bug/1583849/+subscriptions
>

Revision history for this message
ernsteiswuerfel (erhard-f) wrote :

Yes, Firefox is in Xenial's repository but not in Yakkety's or Zesty's:
http://packages.ubuntu.com/search?suite=zesty&arch=powerpc&mode=exactfilename&searchon=contents&keywords=firefox

Revision history for this message
Fritz Hudnut (este-el-paz) wrote :

For my PPC machines I'm thinking Xenial is the "final destination" . . . on
my 933 MHz iBook, everything loads very slowly . . . not even thinking
about non-LTS options for them.

On Mon, Dec 12, 2016 at 10:36 AM, ernsteiswuerfel <email address hidden>
wrote:

> Yes, Firefox is in Xenial's repository but not in Yakkety's or Zesty's:
> http://packages.ubuntu.com/search?suite=zesty&arch=
> powerpc&mode=exactfilename&searchon=contents&keywords=firefox
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1583849
>
> Title:
> Firefox > 44 is broken on all big-endian architectures
>
> Status in Mozilla Firefox:
> Fix Released
> Status in firefox package in Ubuntu:
> Confirmed
>
> Bug description:
> OK, the reason I'm posting back here, running Lu 16.04 on an PPC
> iBook, and MATE/XFCE 16.04 on a PM ST. . . did a dist-upgrade today,
> so it now running the new "22" kernel and saw in the list of upgrades
> new updates to FF and T-bird . . . on both machines after reboot FF
> window frame loads . . . and then crashes . . . no data is ever filled
> into the browser window.
>
> The iBook error says it "doesn't have enough memory to report the
> problem" . . . and on the PM . . . apparently it says the error report
> was "corrupted" . . . no launchpad window opened in the browser when I
> clicked on the "report the problem."
>
> Tried to revert to the old kernel in the iBook several times,
> seemingly failed to boot the old one . . . shut it down.
>
> I went to the PM running 16.04 U-MATE and tried the same dist-upgrade
> via console there, that upgrade was much larger than the Lu system,
> but subsequently FF also then failed to launch w/o crashing . . .
> installed Midori to make an apple user post, but when I tried to start
> a new thread there Midori crashed as well.
>
> I ran "apt-get -f install" in both the iBook & the PM . . . nothing
> showed up. No "comment" in the terminal during the upgrade asking any
> questions or reporting "problems" . . . but FF is kaput!!!!
>
> I'm back in OSX 10.5 side until things cool down for the browsers in
> 16.04 PPC Lu & U-MATE/XFCE.
>
> e...
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/firefox/+bug/1583849/+subscriptions
>

Revision history for this message
In , Merlijn-v (merlijn-v) wrote :

I don't understand why this is marked as fixed. None of the issues linked from this issue are fixed. And I am running into this issue both on Firefox 45.6.0 and 50.1.0, on PPC64 (Big endian) Gentoo.

Revision history for this message
In , John Paul Adrian Glaubitz (glaubitz) wrote :

(In reply to Merlijn B.W. Wajer from comment #7)
> I don't understand why this is marked as fixed. None of the issues linked
> from this issue are fixed. And I am running into this issue both on Firefox
> 45.6.0 and 50.1.0, on PPC64 (Big endian) Gentoo.

I didn't try big-endian PPC64, but at least sparc64 - which is also big-endian - works fine. I did not see any crashes.

Revision history for this message
In , Merlijn-v (merlijn-v) wrote :

OK. On PowerPC it is not fixed, as far as I can tell.

firefox 50.1.0 in debian sid gives these errors:

Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 1 (t=3.55253) |[6406][GFX1]: Unknown image format 1 (t=72.1646) |[6407][GFX1]: Unknown image format 0 (t=72.1647) |[6408][GFX1]: Unknown image format 1 (t=72.1648) |[6409][GFX1]: Unknown image format 0 (t=72.165) |[6410][GFX1]: Unknown image format 1 (t=72.1812) |[6411][GFX1]: Unknown image format 1 (t=72.1814) |[6412][GFX1]: Unknown image format 1 (t=72.1816) |[6413][GFX1]: Unknown image format 0 (t=72.1817) |[6414][GFX1]: Unknown image format 1 (t=72.1818) |[6415][GFX1]: Unknown image format 0 (t=72.182) |[6401][GFX1]: Unknown image format 0 (t=72.1484) |[6402][GFX1]: Unknown image format 1 (t=72.1485) |[6403][GFX1]: Unknown image format 0 (t=72.1487) |[6404][GFX1]: Unknown image format 1 (t=72.1642) |[6405][GFX1]: Unknown image format 1 (t=72.1644) [GFX1]: Unknown image format 0

Gentoo 45.6.0 and 50.1.0 exhibits the same errors.

Should I file a new bug? It seems awfully related.

Revision history for this message
In , Martin Husemann (ub71a5bwcb7k-6kfa0n-b69y0hv8hgzd) wrote :

I see the same error output on sparc64, but previously it caused real rendering fallout (like redrawing the whole tree on every error), which does not happen anymore.

Since I usually do not monitor stderr/stdout from firefox during daily usage, I did not notice earlier.

Revision history for this message
In , Martin Husemann (ub71a5bwcb7k-6kfa0n-b69y0hv8hgzd) wrote :

Merlijn: please feel free to reopen, I guess "fixed" is overstated in this context.

Revision history for this message
In , Alex Perez (aperez-6) wrote :

I am also experiencing this exact same problem. Will someone who has the ability please re-open this bug?

Bug Watch Updater (bug-watch-updater)
Changed in firefox:
status: Fix Released → Confirmed
Revision history for this message
In , Alex Perez (aperez-6) wrote :

Thanks!

Revision history for this message
In , Christian Zigotzky (chzigotzky-xenosoft) wrote :

Hi All,

I have Debian Sid PowerPC (PPC32) on my A-EON AmigaOne X1000 Nemo (P.A. Semi PA6T). I have the same problems with Firefox.

Cheers,
Christian

Revision history for this message
In , Stransky (stransky) wrote :

It may be related:
https://bugzilla.redhat.com/show_bug.cgi?id=1423012

Revision history for this message
In , John Paul Adrian Glaubitz (glaubitz) wrote :

Here's the backtrace I am getting with Firefox 59 on sparc64:

Thread 1 "firefox" received signal SIGSEGV, Segmentation fault.
0xfff8000109aea030 in ContextToPC (context=0x7feffffa790)
    at /srv/glaubitz/firefox-59.0~b4/js/src/wasm/WasmSignalHandlers.cpp:434
434 MOZ_CRASH();
(gdb) bt
#0 0xfff8000109aea030 in ContextToPC (context=0x7feffffa790)
    at /srv/glaubitz/firefox-59.0~b4/js/src/wasm/WasmSignalHandlers.cpp:434
#1 0xfff8000109aea030 in RedirectJitCodeToInterruptCheck (context=0x7feffffa790, cx=<optimized out>)
    at /srv/glaubitz/firefox-59.0~b4/js/src/wasm/WasmSignalHandlers.cpp:1510
#2 0xfff8000109aea030 in JitInterruptHandler(int, siginfo_t*, void*) (signum=<optimized out>, info=0x7feffffa790, context=0x7feffffa790)
    at /srv/glaubitz/firefox-59.0~b4/js/src/wasm/WasmSignalHandlers.cpp:1561
#3 0xfff800010013bf5c in <signal handler called> ()
    at ../sysdeps/unix/sysv/linux/sparc/sparc64/sigaction.c
#4 0xfff80001009af594 in __GI___poll (fds=0x7feffffab68, nfds=1, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:29
#5 0xfff8000103c53bd0 in () at /usr/lib/sparc64-linux-gnu/libxcb.so.1
(gdb)

I have tried Martin's patch from the RedHat bugzilla, but so far it didn't help. But I just did a quick incremental build and may need a full rebuild which I am trying now.

Revision history for this message
In , John Paul Adrian Glaubitz (glaubitz) wrote :

Oh, wait a second. This crash happens because we are missing an implementation for sparc64 here:

static uint8_t**
ContextToPC(CONTEXT* context)
{
#ifdef KNOWS_MACHINE_STATE
    return reinterpret_cast<uint8_t**>(&PC_sig(context));
#else
    MOZ_CRASH();
#endif
}

js/src/wasm/WasmSignalHandlers.cpp

Norbert (nrbrtx)
Changed in firefox (Ubuntu):
status: Confirmed → Incomplete
Bug Watch Updater (bug-watch-updater)
Changed in firefox:
importance: Medium → Unknown
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.