Great , thank you ! I have a special build of skia dir I will try this
into your build and see if it will work with skia asm anabled . Thanks
again for hard work !
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
I never talked with a ubuntu package manager and I do not know anybody
... I have a HTC 10 phone with 4 gb ram that I can use to try to build
firefox on it . I did not used it till now cacse I use it without swap
and firefox team say we need at least 8 gb ram to compile ff . Are you
sure 2 gb ram
If you have a good intel cpu and 16 gb ram ,you can just install using sbuild
the trusty armhf and use it to compile . It will take no more than 3 days to
compile on a i7 intel cpu .
It will take longer than it took inside my real arm hardware because it use
qemu , but will not take more than
We think CFLAGS="-march=armv7-a -mfloat-abi=hard -mfpu=vfpv3-d16" will prevent
the skia crash .
But firefox must be build using trusty cause xenial builds have at least 2
crashes . (skia and smth else) .
The trusty build crash just if skia is enabled and we think building
firefox using trusty
But there is a big hope the build for trusty with "-march=armv7-a
-mfloat-abi=hard -mfpu=vfpv3-d16" will not crash .Builing on xenial
did nto worked but a build in trusty have great chances to work .
--
You received this bug notification because you are a member of Desktop
Packages, which
Ok , I did not tried firefox 59 but my firefox 58.02armhf build with
this options "-march=armv7-a -mfloat-abi=hard -mfpu=vfpv3-d16" was
compiled fine by gcc under Ubuntu 16.04 and there was still a crash .
You can read the crah cause I post earlier . Is not the skia crash , is another
one that
Can you check if the firefox 57.04 trusty , the working one shows
"-march=armv7-a -mfloat-abi=hard -mfpu=vfpv3-d16" in about:buildconfig ?
I'm thinking that "-march=armv7-a -mfloat-abi=hard -mfpu=vfpv3-d16" are
automaticaly added when you build something with gcc in Ubuntu armhf .
--
You
firefox_57.0.4 ubuntu xenial crash like firefox 58 ubuntu xenial , before it
reach skia bug
=> 0xf4cd4790: strdr2, r3, [r1]
0xf4cd4794: ldr.w r3, [r9, #4]
0xf4cd4798: addsr3, #123; 0x7b
0xf4cd479a: beq.w 0xf4cd4a34
0xf4cd479e: ldr r1, [r6, #24]
I run firefox 58.02 armhf that comes with ubuntu 16.04 and it crash in
same point my custom firefox 58.02 crashed :
Thread 1 "firefox" received signal SIGSEGV, Segmentation fault.
0xf4c3bfc4 in JS::MutableHandle::set (v=..., this=)
at
I will install default ubuntu xenial firefox_58.0.2 and see if that crash on a
different asm instruction than my custom build and I will report .
By the way I managed to set up a cross compile development , now I compile it
with a intel cpu and is a lot faster . So a lot of testing can be made .
@james you said in a old post
"You can actually hexedit libxul.so and change those four vorr
instructions into NOPs. Firefox then makes it past this point but
crashes obscurely elsewhere, with different crash signatures on Firefox
58 vs 59."
Can you check where that "crashes obscurely
I tried yesterday java.script.enabled false in prefs.js and it still crashed ,
same crash .
i will try also javascript.options.baselinejit false ;
You know firefox 57.04 armhf , did not used sk jumper generated code
with skia disabled in prefs.js and worked fine .
I have to see if there was
Maybe because it do not crash on skia anymore , this crash in
RootingAPI.h will be easier to 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/1711337
Title:
Firefox crashes at
I installed debug symbols here are more crash about the crash , again
like i said is not in skia anymore :
Thread 1 "firefox" received signal SIGSEGV, Segmentation fault.
0xf4c3dcb4 in JS::MutableHandle::set (v=..., this=) at
It successfully build a deb .I build all with gcc except gfx/skia build with
clang .
There is again a crash but It looks now is not in _sk_xor__vfp4 the asm code
where it crash is different from the asm code of _sk_xor__vfp4 .
firefox -g
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
Copyright
Thanks Chris that is hopeful to know .
As a summary for all I did and some notes :
Compiling firefox with clang was fine ,just required some -std=xxx adaption.
But after it finish to compile it try to make libxul.so by linking libs and it
fail to link libstagefright teling me it can not find
I can not pass pass about this linking problem , because re running the
build process is very time consuming . Any way I will let it build with
gcc and I will replace in gcc build the gfx/skia dir with the one build
by clang .
--
You received this bug notification because you are a member of
When it link libxul.so it get a linker error :
1013:18.63 ../../media/libstagefright/Unified_cpp_media_libstagefright1.o: In
function `operator delete(void*)':
1013:18.64
/root/firefox-58.0.2+build1/obj-arm-linux-gnueabihf/dist/include/mozilla/mozalloc.h:230:
undefined reference to `free'
And that why gdb do not recognize it as a instruction set . We have just
to wait few for the compile to finish and I'll tell you if it really
works .It is very close to building libxul.so right now .
--
You received this bug notification because you are a member of Desktop
Packages, which is
So I heve the strong feeling that here the crash in skia comes from . If
"-mfloat-abi=hard -mtune=generic-armv7-a -mfpu=vfpv3-d16 -mthumb" is not
passed to clang/gcc , then it does not recognize that part of the
binary content as an instruction and it just displays it as if it were
a 32-bit data
Hmm very interesting . I also objdump -d SkJumper_generated.o ( build by clang
without "-mfloat-abi=hard -mtune=generic-armv7-a -mfpu=vfpv3-d16 -mthumb" )
and is different result .
0318 <_sk_xor__vfp4>:
318: f2c70f10.word 0xf2c70f10
31c: e4913004
I disasm the SkJumper_generated.o generated by clang : objdump -d
SkJumper_generated.o
0318 <_sk_xor__vfp4>:
318: f2c70f10vmov.f32d16, #1 ; 0x3f80
31c: e4913004ldr r3, [r1], #4
320: f2603d83vsub.f32d19, d16, d3
Also in firefox-58.0.2+build1/obj-arm-linux-
gnueabihf/gfx/skia/backend.mk on the last line I also have added
"-mfloat-abi=hard -mtune=generic-armv7-a -mfpu=vfpv3-d16 -mthumb" hoping
to fix the crash in skia . Will see in few hours if will still crash or
not ...
--
You received this bug
Here is what I did .
apt-get install build-essential fakeroot devscripts
apt-get build-dep firefox
apt-get install icecc
apt-get install clang-5.0
apt-get install python-dev
apt-get source firefox
cd firefox-58.0.2+build1/
export CC=clang-5.0
export CXX=clang++-5.0
export CCACHE_PREFIX=icecc
The good news is that I just had to modify the "-std=" just in 4 places and all
compiled fine .
The bad one is that I received a "Memory exausted" error when it build
libxul.so .
But I upgraded the machine from 8 gb of RAM to 16 gb of RAM and in 2-3 hours it
will try again to build libxul.so
_sk_xor__vfp4 asm code is thumb2 code so maybe if gcc will be instructed
to compile it as a thumb2 code will work also to compile with gcc .
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
Can the firefox build be instructed to build only libxul.so ? This will
be a faster compile than to build all . I was thinking to build just
that with clang and replace this inoriginal deb.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Firefox looks to dnt get compiled by clang out of the box without intervention.
I got some errors like :
87:09.20 In file included from
/root/firefox-58.0.2+build1/media/libpng/arm/filter_neon_intrinsics.c:22:
87:09.22 /usr/lib/llvm-4.0/bin/../lib/clang/4.0.0/include/arm_neon.h:433:1:
error:
Thanks @Cris for link , but fortunately my configure step passed and all was
fine .
It started to compile is is still compiling for 1:30 hours already .
I did not had that problem ,firefox compile but is very show .I hope will be no
errors .
Let's hope building with clang will fix that skia
I confirm they really use clang when they build chromium and they do not cross
compile it .
So I have a strong feeling if we compile firefox with clang will work and will
be no crash .
My machine is building using clang but will take maybe 1 day to finish.
I see the firefox build for ubuntu devs
Ok , I started to compile it using clang :
0:55.76 checking for pkg_config... /usr/bin/pkg-config
0:55.80 checking for pkg-config version... 0.29.1
0:55.82 checking for yasm... /usr/bin/yasm
0:55.86 checking yasm version... 1.3.0
0:55.94 checking the target C compiler version... 3.8.0
My last feeling ,is it just a aarch64 kernel with a arm64 Ubuntu xenial and
enabled multiarch so it downloads the armhf build deps . Any way like you said
, maybe a build with clang will fix it .
Let;s hope there will be a way to finaly have latest firefox on armhf .
Thank you for your interest
@James Donald (jdonald) thanks for your reply .All you say is very interesting
by my remark is that I think ubuntu do not cross compile firefox for armhf ,
they just use a aarch64 (arm 64 bit ) kernel and they run a armhf Ubuntu .
I 'm not the expert but from what I talked to others they said
Also I think I'm right it is not cross compiled , you can see at the end of
build log :
+--+
| Summary |
They at chromium say they use clang when they cross compile chromium .And they
had exactly same problem like firefox have ,when they build chromium native
using gcc .
You can read a irc log :
[16:17:16] This has been puzzling us for a few weeks already because
we can't
*** This bug is a duplicate of bug 1711337 ***
https://bugs.launchpad.net/bugs/1711337
I read on chromium forum that they had exaclty this problem too , with
the crash on skia and this problem do not appear if they crosscompiled
chromium , so maybe the solution is to cross compile firefox too
I read on chromium forum that they had exacty this problem too , with
the crash on skia and this problem do not appear if they crosscompiled
chromium , so maybe the solution is to cross compile firefox too .
--
You received this bug notification because you are a member of Desktop
Packages,
So "firefox_57.0.1+build2-0ubuntu0.16.04.1_armhf.deb" is working ?
--
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/1711337
Title:
Firefox crashes at start on armv7L after 55.0.1
38 matches
Mail list logo
