Package Details: firefox-esr-i18n-oc 115.10.0-1

Git Clone URL: https://aur.archlinux.org/firefox-esr.git (read-only, click to copy)
Package Base: firefox-esr
Description: Standalone web browser from mozilla.org, Extended Support Release
Upstream URL: https://www.mozilla.org/en-US/firefox/enterprise/
Keywords: browser gecko web
Licenses: GPL, MPL, LGPL
Submitter: figue
Maintainer: dudemanguy
Last Packager: dudemanguy
Votes: 47
Popularity: 0.44
First Submitted: 2015-05-28 23:15 (UTC)
Last Updated: 2024-04-16 22:28 (UTC)

Dependencies (37)

Required by (0)

Sources (100)

Latest Comments

« First ‹ Previous 1 .. 12 13 14 15 16 17 18 19 20 Next › Last »

klemens commented on 2017-09-08 19:06 (UTC)

I was able to debug myself through the code of the crashing site that I originally encountered and produce a minimal example that reliably crashes the current tab for me: [1] @figue: Could you please verify that this also crashes for you? I will then go ahead and report the bug. [1]: http://asa.crpt.de/files/crash-firefox-esr.html

figue commented on 2017-08-29 15:00 (UTC)

New release to fix crashreporter build.

figue commented on 2017-08-28 15:30 (UTC) (edited on 2017-08-28 15:34 (UTC) by figue)

Ok just forgot to remove !strip. I'll check release 4 again without it. Still bigger, but better now.

figue commented on 2017-08-27 21:17 (UTC)

Ok. Do it please... I understand the huge file, but I don't know why without building symbols is huge too... If you want to check my sources... http://figue.lnx.im/PKGBUILDs/firefox-esr-52.3.0-4.src.tar.gz

klemens commented on 2017-08-27 21:16 (UTC)

@figue: libxul.so being so huge is pretty normal when it has debugging information included (mine was around 1,2 GiB). When you attach a gdb, you will get a backtrace with symbols when it crashes (disabling multiprocess makes it much easier to capture). For the symbols on crash-stats.mozilla.com to resolve correctly, you probably need to upload the generated *crashreporter-symbols.zip file. I think I will just open a bug report at mozilla with my gdb backtrace and the two crash reports.

figue commented on 2017-08-27 21:05 (UTC) (edited on 2017-08-27 21:16 (UTC) by figue)

@klemens mmm I think I made some mistake... libxul.so is huge... Let me check it. https://crash-stats.mozilla.com/report/index/d286d38a-295e-4d73-8d49-c74251170827#tab-details

klemens commented on 2017-08-27 19:03 (UTC)

@figue: Did your crash report include symbols? You can view all sent reports using about:crashes.

figue commented on 2017-08-27 18:56 (UTC) (edited on 2017-08-27 18:57 (UTC) by figue)

Hi @klemens, I have crashreporter working again. I could sent the crash to Mozilla. I'm building Firefox again without symbols, because package with symbols is more than 1 GB... (it's the release 52.3.0-3). Will push my changes to AUR's git later if you want to make more tests.

klemens commented on 2017-08-26 17:48 (UTC)

@figue: I tried to make the crash reporter work [1], but this may not be the right approach, as everyone would have to upload their symbols package to crash-stats.mozilla.com, for which you need an auth token. So I suggest removing `mach buildsymbols` again. However, I was able to get a backtrace of the crash with symbols using gdb [1]. [1]: https://gist.github.com/klemens/15aec97e5f6c22d3b3bddb39048cd280

figue commented on 2017-08-24 23:57 (UTC) (edited on 2017-08-25 08:09 (UTC) by figue)

@klemens can you try the new release? Edit: Forget it, still crash. I've disabled a couple of system libraries in the build and switched to "mach build", but I can't add "find . -name '*crashreporter-symbols-full.zip' -exec cp -fvt "$startdir" {} +" because crashreporter fails to build in two of my machines, so I've disabled it. If it's too important for you, you can try to add "find . -name '*crashreporter-symbols-full.zip' -exec cp -fvt "$startdir" {} +" in package() and enable crashreporter, build and then debug the crash and send it to upstream. Good luck!

« First ‹ Previous 1 .. 12 13 14 15 16 17 18 19 20 Next › Last »