Package Details: firefox-esr-i18n-hu 128.5.2-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: 48
Popularity: 0.082451
First Submitted: 2015-05-28 23:15 (UTC)
Last Updated: 2024-12-13 15:57 (UTC)

Required by (0)

Sources (100)

Latest Comments

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

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!

klemens commented on 2017-08-24 15:12 (UTC) (edited on 2017-08-24 15:20 (UTC) by klemens)

@figue: It had been the first time that I built this package. I just rebuilt it and the error persists. I also uploaded the crash report [1], but it doesn't contain symbols, so it is rather useless. However I am not sure how to build the package with symbols or how to use them if they are already included. Edit: It seems symbols have to be created and uploaded separately: [2] [1]: https://crash-stats.mozilla.com/report/index/412d2adb-ff81-4cda-ba55-bc4f41170824#tab-details [2]: https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/firefox&id=384274d92b096f95ab46bfd17ded75815f67aac3

figue commented on 2017-08-24 14:28 (UTC) (edited on 2017-08-24 14:29 (UTC) by figue)

@klemens that URL craches my Firefox ESR too. Not much is dump in console: Promise rejected after context unloaded: Message manager disconnected Promise rejected after context unloaded: Message manager disconnected ExceptionHandler::GenerateDump cloned child 22028 ExceptionHandler::WaitForContinueSignal waiting for continue signal... ExceptionHandler::SendContinueSignalToChild sent continue signal to child With NoScript activated, page loads just "fine", is when I allow all the scripts from that domain that Firefox crash. Did you rebuild Firefox recently to see if some library update is causing the crash?

figue commented on 2017-08-19 08:24 (UTC)

@klemens I'm on vacation until next monday, so I can't test now. But you can try to rebuild Firefox, maybe a library update makes it crash... But without logs it's hard to say.

ben81 commented on 2017-08-18 19:13 (UTC)

@klemens, that website did not crash my Firefox ESR 52.3.0. However, I have Manjaro, not Arch. Maybe that’s the difference.

klemens commented on 2017-08-17 20:15 (UTC)

Opening [1] reliably crashes the current tab for me, even with a clean new profile, while firefox-esr-bin seems to work fine. Does it crash for anyone else? [1]: https://www.soeren-hentzschel.at/firefox/neues-logo-firefox-und-firefox-klar/

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