Summary: | www/firefox: crashes on certain sites | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | robert.ayrapetyan | ||||
Component: | Individual Port(s) | Assignee: | freebsd-gecko (Nobody) <gecko> | ||||
Status: | Closed Overcome By Events | ||||||
Severity: | Affects Only Me | CC: | dim.jakobi, grahamperrin, nrgmilk, srlemke, w.schwarzenfeld | ||||
Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(gecko) |
||||
Version: | Latest | ||||||
Hardware: | amd64 | ||||||
OS: | Any | ||||||
See Also: | https://bugzilla.mozilla.org/show_bug.cgi?id=1476130 | ||||||
Attachments: |
|
Description
robert.ayrapetyan
2018-06-09 21:58:52 UTC
I can't reproduce. Maybe try Firefox 61 from review D15227. > Chrome doesn't crash immediately, but reboots PC after performing some browsing there... Did you mean www/chromium ? If so it could be due to a kernel panic e.g., in GPU drivers. Maybe try graphics/drm-stable-kmod. Not reproducible here with Firefox 61.0_1,1 on FreeBSD-CURRENT $ uname -a FreeBSD momh167-gjp4-hpelitebook8570p-freebsd 12.0-CURRENT FreeBSD 12.0-CURRENT #6 r335800: Sat Jun 30 03:35:14 BST 2018 root@momh167-gjp4-hpelitebook8570p-freebsd:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 It still crashes on random sites on random actions, I can't find a stable way to reproduce this issue, but it crashes once or twice per day. FreeBSD 11.2-RELEASE-p1 Firefox 61.0.1 (64-bit) (installed from packages) Core was generated by `/usr/local/lib/firefox/firefox -contentproc -childID 4 -isForBrowser -prefsLen 3'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x000000080d57eab9 in mozilla::ipc::MessageChannel::OnChannelErrorFromLink() () from /usr/local/lib/firefox/libxul.so [Current thread is 1 (LWP 100810)] (gdb) bt #0 0x000000080d57eab9 in mozilla::ipc::MessageChannel::OnChannelErrorFromLink() () from /usr/local/lib/firefox/libxul.so #1 0x000000080d580000 in non-virtual thunk to mozilla::ipc::ProcessLink::OnChannelError() () from /usr/local/lib/firefox/libxul.so #2 0x000000081453106f in ?? () from /usr/local/lib/libevent-2.1.so.6 #3 0x000000081452cf4e in event_base_loop () from /usr/local/lib/libevent-2.1.so.6 #4 0x000000080d556438 in base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) () from /usr/local/lib/firefox/libxul.so #5 0x000000080d554f7c in MessageLoop::Run() () from /usr/local/lib/firefox/libxul.so #6 0x000000080d55fa4d in base::Thread::ThreadMain() () from /usr/local/lib/firefox/libxul.so #7 0x000000080d55a5ba in ThreadFunc(void*) () from /usr/local/lib/firefox/libxul.so #8 0x0000000801da3c06 in ?? () from /lib/libthr.so.3 #9 0x0000000000000000 in ?? () Backtrace stopped: Cannot access memory at address 0x7fffdfffe000 What could be the reason for that? Thanks. A commit references this bug: Author: jbeich Date: Wed Sep 26 16:05:49 UTC 2018 New revision: 480744 URL: https://svnweb.freebsd.org/changeset/ports/480744 Log: www/firefox: document e10s instability PR: 225233 228855 Changes: head/www/firefox/pkg-message head/www/firefox-esr/pkg-message head/www/waterfox/pkg-message A commit references this bug: Author: jbeich Date: Wed Sep 26 16:06:50 UTC 2018 New revision: 480745 URL: https://svnweb.freebsd.org/changeset/ports/480745 Log: MFH: r480744 www/firefox: document e10s instability PR: 225233 228855 Approved by: ports-secteam blanket Changes: _U branches/2018Q3/ branches/2018Q3/www/firefox/pkg-message branches/2018Q3/www/firefox-esr/pkg-message branches/2018Q3/www/waterfox/pkg-message Seems it has started to crash again (Firefox 63.0.1 (64-bit)): Core was generated by `/usr/local/lib/firefox/firefox -contentproc -childID 3 -isForBrowser -prefsLen 1'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x000000080d1fbb39 in mozilla::ipc::MessageChannel::OnChannelErrorFromLink() () from /usr/local/lib/firefox/libxul.so [Current thread is 1 (LWP 101784)] (gdb) bt #0 0x000000080d1fbb39 in mozilla::ipc::MessageChannel::OnChannelErrorFromLink() () from /usr/local/lib/firefox/libxul.so #1 0x000000080d1fd020 in non-virtual thunk to mozilla::ipc::ProcessLink::OnChannelError() () from /usr/local/lib/firefox/libxul.so #2 0x0000000814378ecd in ?? () from /usr/local/lib/libevent-2.1.so.6 #3 0x0000000814374e1f in event_base_loop () from /usr/local/lib/libevent-2.1.so.6 #4 0x000000080d1d3908 in base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) () from /usr/local/lib/firefox/libxul.so #5 0x000000080d1d246c in MessageLoop::Run() () from /usr/local/lib/firefox/libxul.so #6 0x000000080d1dcbcd in base::Thread::ThreadMain() () from /usr/local/lib/firefox/libxul.so #7 0x000000080d1d7967 in ThreadFunc(void*) () from /usr/local/lib/firefox/libxul.so #8 0x0000000801da4c06 in ?? () from /lib/libthr.so.3 #9 0x0000000000000000 in ?? () Backtrace stopped: Cannot access memory at address 0x7fffdfffe000 Same here: firefox-63.0.1_1,1 installed via pkg Is this still relevant? Switched to Chrome lol Jan Beich suggested as workaround "sysctl net.local.stream.recvspace=16384". Created attachment 208119 [details]
Core.txt.0_crash
Firefox crashes on Goggle Maps Street View, Satellite View. FreeBSD 12.1-STABLE FreeBSD 12.1-STABLE r353110 GENERIC amd64 Firefox 69.0.2,1 ATI HD5040 Steps to reproduce: Open a map on Google Maps. Choose Street View or Satellite View. Navigate on the map for some time without a break. It takes about 20 moves till Firefox crashes and the system reboots. That's sad. On my system, not only Firefox but also Chromium causes a segmentation fault & reboot when using Street View in a swiftly. firefox-71.0_4,1@12.1-STABLE r355882 has crashed tab at google street view. Map and satellite, 3D are ok. [Parent 65426, Gecko_IOThread] WARNING: pipe error: Broken pipe: file /tmpfs/usr/ports/www/firefox/work/firefox-71.0/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 728 Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: DrawTargetCairo::Snapshot with bad surface 0x821282f80, context 0x81f42d600, status 0 (t=118.149) [GFX1-]: DrawTargetCairo::Snapshot with bad surface 0x821282f80, context 0x81f42d600, status 0 (In reply to nrgmilk from comment #15) May be driver-specific. I can't reproduce either on native X11, XWayland or Wayland compositor. (In reply to Jan Beich from comment #16) After reboot, the symptom has not been happend. Is this still reproducible? Food for thought: bug 260387 comment 7 with regard to limits. |