Re: [blfs-support] Firefox-68 crashes
On Tue, Jun 02, 2020 at 02:57:22PM -0400, Richard via blfs-support wrote: > > I have tried both firefox-68.5.0 and firefox-68.8.0 > in blfs-9.1, and both of them are unusable because > they crash at startup. Unfortunately I have to use > the pre-compiled versions because my system is > no longer capable of building firefox, but I have > done this in past versions without any problems. Yeah, been there in the past - but at least you don't spend hours compiling it (although I'm not exactly sure that a non-working binary actually counts as an improvement). > Since I am not building firefox I guess I can't > really expect much help, but I thought I would > just list the typical output I get at startup -- I am > hoping someone has maybe seen similar output > and can suggest what might be the problem. > Also, any suggestions how I might troubleshoot > the problem would be helpful. > I get many lines like the following at startup: > > [Parent 757, Gecko_IOThread] WARNING: pipe error (68): Connection reset by > peer: file > /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, > line 358 > [Parent 757, Gecko_IOThread] WARNING: pipe error (79): Connection reset by > peer: file > /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, > line 358 > A lot in google (not all necessarily for firefox), on a quick glance the main suspects seem to be X11 forwarding and add-ons or extensions. > 2020-05-31 14:32:50: minidump.cc:1571: ERROR: MinidumpThread has a memory > region problem, 0xbf712e60+0x0, RVA 0x0x338 And for that, no obvious common features except that restarting without add-ons and extensions is again suggested. Oh, and some instances where people were running kde as their desktop. But for both, many of the reports are quite old (I think the newest I looked at was for firefox-71 which is at least 6 months ago). Of course, if you don't have any other systems or graphical browsers then searching in google or duckduckgo is quite problematic. > 2020-05-31 14:32:50: minidump_processor.cc:255: ERROR: No memory region for > /root/.mozilla/firefox/Crash Hmm, you're trying to run it as root ? If the X session is owned by your regular user, you can't do that. And running X as root, except (perhaps) for initial testing on a new build, is a bad idea. > Reports/pending/67ce34e7-0dcd-9d48-1162-302034561b57.dmp:0/13 id 0x31c > 2020-05-31 14:32:50: stackwalker_x86.cc:631: ERROR: Can't get caller frame > without memory or stack > I expect that last error is because everything has already fallen over. Like compilation failures: the first error matters, later errors may be irrelevant and/or misleading. More generally, if you have to use the binary then once you get it working I suggest you use the latest 'stable' release (e.g. as of today that would be 77.0). When I used to use the binary on my old 32-bit netbook ISTR that it would download a new version within a few days of a release. The only reason we're using ESR in BLFS is to keep the same version of rustc for all packages that use rust (cbindgen, firefox, librsvg, seamonkey, thunderbird). Good luck. ĸen -- +++ OUT OF CHEESE ERROR. REDO FROM START +++ -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Firefox-68 crashes
On Tue, 2020-06-02 at 14:57 -0400, Richard via blfs-support wrote: > I have tried both firefox-68.5.0 and firefox-68.8.0 > in blfs-9.1, and both of them are unusable because > they crash at startup. Unfortunately I have to use > the pre-compiled versions because my system is > no longer capable of building firefox, but I have > done this in past versions without any problems. > Since I am not building firefox I guess I can't > really expect much help, but I thought I would > just list the typical output I get at startup -- I am > hoping someone has maybe seen similar output > and can suggest what might be the problem. > Also, any suggestions how I might troubleshoot > the problem would be helpful. > I get many lines like the following at startup: > > [Parent 757, Gecko_IOThread] WARNING: pipe error (68): Connection > reset > by peer: file > /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc > _channel_posix.cc, > line 358 > [Parent 757, Gecko_IOThread] WARNING: pipe error (79): Connection > reset > by peer: file > /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc > _channel_posix.cc, > line 358 > > 2020-05-31 14:32:50: minidump.cc:1571: ERROR: MinidumpThread has a > memory region problem, 0xbf712e60+0x0, RVA 0x0x338 > 2020-05-31 14:32:50: minidump_processor.cc:255: ERROR: No memory > region > for /root/.mozilla/firefox/Crash > Reports/pending/67ce34e7-0dcd-9d48-1162-302034561b57.dmp:0/13 id > 0x31c > 2020-05-31 14:32:50: stackwalker_x86.cc:631: ERROR: Can't get caller > frame without memory or stack Well, very hard to tell without knowing the code. Looks like lack of memory or so. So just 2 quick checks: - do you have some room on the disk? (use "df") - do you have some free memory? (use "free") Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-support] Firefox-68 crashes
I have tried both firefox-68.5.0 and firefox-68.8.0 in blfs-9.1, and both of them are unusable because they crash at startup. Unfortunately I have to use the pre-compiled versions because my system is no longer capable of building firefox, but I have done this in past versions without any problems. Since I am not building firefox I guess I can't really expect much help, but I thought I would just list the typical output I get at startup -- I am hoping someone has maybe seen similar output and can suggest what might be the problem. Also, any suggestions how I might troubleshoot the problem would be helpful. I get many lines like the following at startup: [Parent 757, Gecko_IOThread] WARNING: pipe error (68): Connection reset by peer: file /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358 [Parent 757, Gecko_IOThread] WARNING: pipe error (79): Connection reset by peer: file /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358 2020-05-31 14:32:50: minidump.cc:1571: ERROR: MinidumpThread has a memory region problem, 0xbf712e60+0x0, RVA 0x0x338 2020-05-31 14:32:50: minidump_processor.cc:255: ERROR: No memory region for /root/.mozilla/firefox/Crash Reports/pending/67ce34e7-0dcd-9d48-1162-302034561b57.dmp:0/13 id 0x31c 2020-05-31 14:32:50: stackwalker_x86.cc:631: ERROR: Can't get caller frame without memory or stack Richard -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
