Closing
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1850529
Title:
Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1
Status in Mozilla Firefox:
Won't Fix
Status in firefox
** Changed in: firefox
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1850529
Title:
Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1
Un-assigning for now. There seem to be arguments for and against here,
but if we're sure people aren't hitting this anymore this should be
closed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
** Bug watch added: Mozilla Bugzilla #1600467
https://bugzilla.mozilla.org/show_bug.cgi?id=1600467
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1850529
Title:
Crash after update
*** Bug 1597006 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1850529
Title:
Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1
It's very possible this is the same as bug 1601707. If it is, we don't
need to exclude clang 6.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1850529
Title:
Crash after update to
(In reply to Nathan Froyd [:froydnj] from comment #19)
> (In reply to Mike Hommey [:glandium] (high latency) from comment #18)
> > It's very possible this is the same as bug 1601707. If it is, we don't need
> > to exclude clang 6.
>
> OTOH, I don't want to be rediscovering that people are using
I ended up writing a patch for this. I'll post it in case we end up
wanting to take it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1850529
Title:
Crash after update to
(In reply to Chris Manchester (:chmanchester) from comment #15)
> I'll take this. dmajor, does it seem worthwhile to explicitly check for the
> clang 6 from automation case? Just disallowing clang-6 seems more
> straightforward.
So you're proposing that our clang requirement on Linux would be
Maybe even tier 2 / running on m-c only, or something?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1850529
Title:
Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1
Status in
(In reply to :dmajor from comment #16)
> (In reply to Chris Manchester (:chmanchester) from comment #15)
> > I'll take this. dmajor, does it seem worthwhile to explicitly check for the
> > clang 6 from automation case? Just disallowing clang-6 seems more
> > straightforward.
>
> So you're
This is being tracked by
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1850529 in Ubuntu.
Ubuntu 16.04 has clang 6.0, and as pointed out this is known to result in
miscompilation issues, which for some reason haven't really surfaced until now
(firefox 71). I have tested backporting
Someone on #introduction mentioned that
https://phabricator.services.mozilla.com/D56873 did fix the problem for
them.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1850529
Title:
(In reply to Mike Hommey [:glandium] (high latency) from comment #24)
> (In reply to Nathan Froyd [:froydnj] from comment #19)
> > (In reply to Mike Hommey [:glandium] (high latency) from comment #18)
> > > It's very possible this is the same as bug 1601707. If it is, we don't
> > > need to
(In reply to Emilio Cobos Álvarez (:emilio) from comment #10)
> Ah, thanks for the update Olivier :)
>
> I think it'd still be nice to detect this at configure time if possible, but
> it may be not worth the churn.
I agree - me and a gsoc student were stumped on this for close to a
month,
(In reply to Mike Hommey [:glandium] (high latency) from comment #18)
> It's very possible this is the same as bug 1601707. If it is, we don't need
> to exclude clang 6.
OTOH, I don't want to be rediscovering that people are using a compiler
that doesn't implement some finer point of C++17 (bug
(In reply to Emilio Cobos Álvarez (:emilio) from comment #20)
> (In reply to Nathan Froyd [:froydnj] from comment #19)
> > (In reply to Mike Hommey [:glandium] (high latency) from comment #18)
> > > It's very possible this is the same as bug 1601707. If it is, we don't
> > > need to exclude clang
(In reply to Emilio Cobos Álvarez (:emilio) from comment #21)
> Maybe even tier 2 / running on m-c only, or something?
I'll just note that as somebody who has had multiple patches backed out
because of jobs that *only* run on central and those jobs aren't
selectable by default by `mach try fuzzy`
I'll take this. dmajor, does it seem worthwhile to explicitly check for
the clang 6 from automation case? Just disallowing clang-6 seems more
straightforward.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
(In reply to Nathan Froyd [:froydnj] from comment #19)
> (In reply to Mike Hommey [:glandium] (high latency) from comment #18)
> > It's very possible this is the same as bug 1601707. If it is, we don't need
> > to exclude clang 6.
>
> OTOH, I don't want to be rediscovering that people are using
Oops, wrong needinfo requestee.
(In reply to :Gijs (he/him) from comment #12)
> Can we add a configure check to prevent building with clang 6 unless located
> in `.mozbuild` ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in
(In reply to Mike Hommey [:glandium] (high latency) from comment #24)
> That specific comment explicitly says current GCC doesn't implement it. Are
> we going to require clang only now?
Well GCC just fixed it in fairness:
https://gcc.gnu.org/viewcvs/gcc?view=revision=279069
I think they
Ah, thanks for the update Olivier :)
I think it'd still be nice to detect this at configure time if possible,
but it may be not worth the churn.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
(In reply to Olivier Tilloy from comment #9)
> I am considering attempting a backport of clang 8.
I ended up backporting clang 8 to Ubuntu 16.04, and rebuilding firefox
71.0+build5 with it. The startup crash is gone, and that build was
published to xenial-security and xenial-updates yesterday. So
Created attachment 9115566
Bug 1594686 - Disallow building with clang-6.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1850529
Title:
Crash after update to
Yes I will find an assignee.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1850529
Title:
Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1
Status in Mozilla Firefox:
Thank you Olivier for your effort and the information you provided me as
well.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1850529
Title:
Crash after update to
clang 8 was backported to xenial and firefox 71.0 rebuilt with it, and
the crash is now fixed.
** Changed in: firefox (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
** Changed in: firefox (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1850529
Title:
Crash after update to
** Changed in: firefox (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: firefox (Ubuntu)
Importance: Medium => Critical
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
Applying that patch on top of 1:6.0.1-11 doesn't help, firefox
71.0+build4 still crashes at startup.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1850529
Title:
Crash after update
Can we add a configure check for this somehow? It seems ubuntu almost
ships a build with this bug, see bug 1600467... :/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1850529
Title:
*** Bug 1600467 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1850529
Title:
Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1
I backported clang 1:6.0.1-11 from disco to xenial in a PPA and rebuilt
firefox 71.0+build4 against it, but the crash still occurs at startup.
Version 1:6.0.1-11 from disco doesn't have https://hg.mozilla.org
/mozilla-central/rev/0d04a3f89940536d56cd5415a78316f0960e9f0a, I'll test
applying this
*** Bug 1592571 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1850529
Title:
Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1
In https://bugzilla.mozilla.org/show_bug.cgi?id=1592571, which is currently
identified as a duplicate of
https://bugzilla.mozilla.org/show_bug.cgi?id=1594686, it was pointed out that
this is probably due to bad code generation by clang 6. Two patches for clang 6
which seem to be required to
Simpler than j127's solution is to download the last beta on
https://download.mozilla.org/?product=firefox-beta-latest-
ssl=linux64=en-US, copy your profile into a new folder, then
launch the executable with `MOZ_ALLOW_DOWNGRADE=1
/home/baptiste/firefox/firefox -P`, create a profile and choose the
Launchpad has imported 6 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1594686.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Bug watch added: Mozilla Bugzilla #1594686
https://bugzilla.mozilla.org/show_bug.cgi?id=1594686
** Also affects: firefox via
https://bugzilla.mozilla.org/show_bug.cgi?id=1594686
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
I managed to extract my data from the extensions using the technique I
mentioned in comment #16 above. The process took hours but it worked. If
anyone else's extension data is locked up, try that.
--
You received this bug notification because you are a member of Desktop
Packages, which is
We know that but that does not mean it shouldn't be fixed if this
version is supposed to be released at some point ;-)
Still crashing on 71.0~b8+build1-0ubuntu0.16.04.1 with the same assert
error (MozCrashReason: MOZ_RELEASE_ASSERT(len.isValid()) (Substring
tuple length is invalid)).
--
You
At the risk of repeating myself: the firefox-next PPA is not intended
for production use, only for preview testing of the upcoming version of
firefox. Use at your own risk, or don't use it at all. This is not the
regular Ubuntu archive.
--
You received this bug notification because you are a
Also interesting idea - especially if you need data from extensions
(which I miss too and I didn't try to recover). Also +1 for
blocking/removing this build from download sources. It's too dangerous
for now ;).
--
You received this bug notification because you are a member of Desktop
Packages,
It looks like the only way to get the extension data out of the old
Firefox profiles is to query some sqlite databases that are located in
`/storage/default`. I found one of the important extension
directories, but querying the database just returns gibberish.
For anyone else dealing with the
Thanks, I already downgraded, but the data I need is in the browser
extensions, so I'll look around in those directories. I have three
separate Firefox profiles there that I use on a daily basis.
I still think that if it's known to be broken, it should be removed so
that no one else downloads it.
Yep - fully agree - beta for testing (or for hardcore daily users ;).
Any chances for fix anytime soon anyway?
@j127 - downgrade to latest stable version, find your profile folder
(about:profiles), open the folder with your new profile and copy/paste proper
files from old profile (passwords,
Still crashing with 71.0~b7+build1-0ubuntu0.16.04.1, FWIW.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1850529
Title:
Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1
Status
j127: if you're using the firefox-next PPA, you're doing this at your
own risk, without any guarantees from ubuntu developers that this won't
break. The PPA is meant for testing beta builds, not for end users.
If you want a stable version of firefox, you shouldn't be using that
PPA. Packages in
This broke Firefox for me on 16.04 tonight. Has anyone found a temporary
fix? (It's my main browser with all of my tabs and extension data.)
If "upstream builds of firefox 71.0 beta 5" might work in the meantime,
does anyone know how to install it?
--
You received this bug notification because
Also, if this version is known to be broken, maybe it should be removed
for 16.04 users so that it doesn't happen to anyone else? My computer
downloaded it six days after it was confirmed to be broken.
--
You received this bug notification because you are a member of Desktop
Packages, which is
I confirm the same issue on 16.04. Firefox is now entirely unusable.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1850529
Title:
Crash after update to
Thanks for info - I didn't know that profiles are forward-compatible
only.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1850529
Title:
Crash after update to
I can reliably reproduce the crash in a 16.04 VM. The crash doesn't
occur on 18.04.
Note that this is a beta version of firefox, so use at your own risk
(but the crash will be investigated indeed, thanks for the report!).
Profile incompatibility when downgrading is to be expected. Profiles are
For reference, upstream builds of firefox 71.0 beta 5 are not crashing
in the same xenial VM.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1850529
Title:
Crash after update to
Also important information from my side (as above) - when I try to
restore old version of app: 70.0+build2-0ubuntu0.16.04.1 - I have
information that my profile files are too old and aren't compatible
anymore. So beside update from 70 to 71 - there is something wrong with
profile files
Apologies if I've incorrectly duplicated here - I've logged a separate
bug to ensure there is a full AppPort bundle as suggested in the firefox
bug wiki page.
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1850597
--
You received this bug notification because you are a member of Desktop
Can confirm same issue here - also 16.04 x86_64 - also tried creating a
new (clean) profile, but that does not resolve the issue.
I've reverted off the beta/next ppa back to
"70.0+build2-0ubuntu0.16.04.1", but can't use my old profile as
reverting profiles isn't allowed
--
You received this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: firefox (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
Also I attach crash report from fiferox/profile/crashes folder (I don't
know if it helps but more info is better).
** Attachment added: "76339522-5628-c2f7-1570-0a30605df90f"
Public bug reported:
After update from: 70.0+build2-0ubuntu0.16.04.1 to
71.0~b5+build1-0ubuntu0.16.04.1 app is not starting. I got constantly
message that I can Refresh Firefox (crash) or Start in safe mode (also
crash).
Tech details:
Description:Ubuntu 16.04.6 LTS
Release:16.04
60 matches
Mail list logo
