Discussion:
[gentoo-user] Firefox crashes on some www-pages on a newer Gentoo system
(too old to reply)
gevisz
2018-07-27 08:20:02 UTC
Permalink
I have two Gentoo systems on the same AMD Athlon 64 X2 computer.

The old one was installed in July 2013 with
default/linux/amd64/13.0/desktop/gnome (stable)
profile and was updated till the middle of
July 2017. Initially it hosted Gnome2
but later I have switched to XFCE4.

The new one was installed in January-February 2018
with default/linux/amd64/17.0/desktop (stable)
profile and was last updated yesterday. From the
very beginning it hosted no DE, only Awesome WM
and dbus.

The home directory is the same and still remembers
Ubuntu 6.04 installation in 2006.

On the old system, I had the problem that chromium
very often (but not always!) asked me for some
(keyring?) password when I opened a new www-page.

Recompilation of it with different user flags did not help.

I thought that that was because of the gnome-keyring,
consolekit or policykit packages but without any proof.

So, while installing the new Gentoo system, I decided
to avoid installing any package that needs gnome-keyring,
consolekit or policykit packages.

I have also set -pam -consolekit and -policykit in my
/etc/portage/make.conf

Chromium indeed never asked me for the mentioned
above password on the new Gentoo system.

But I get another problem on the new Gentoo system:
Firefox and Qupzilla both crash on some (login) www-pages.

Namely, Firefox shows the "Gah. Your tab just crashed"
when I try to log into my Yahoo e-mail account.

This happens only after entering login and password,
so not good enough to reproduce.

However, it shows the same message just after staying
about 3-5 seconds on the following internet banking
login page: https://www.privat24.ua/#login
No login or password needed. :)

The last error messages sent to terminal by FF while I
try to open the last www-page are the following:

[Parent 4099] WARNING: pipe error (56): Connection reset by peer: file
/var/tmp/portage/www-client/firefox-52.8.0/work/firefox-52.8.0esr/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
line 322
[Parent 4099] WARNING: pipe error (57): Connection reset by peer: file
/var/tmp/portage/www-client/firefox-52.8.0/work/firefox-52.8.0esr/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
line 322

###!!! [Parent][MessageChannel] Error:
(msgtype=0x2C0083,name=PBrowser::Msg_Destroy) Channel error: cannot
send/recv

[Parent 4099] WARNING: pipe error (44): Connection reset by peer: file
/var/tmp/portage/www-client/firefox-52.8.0/work/firefox-52.8.0esr/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
line 322

###!!! [Parent][MessageChannel] Error:
(msgtype=0x2C0083,name=PBrowser::Msg_Destroy) Channel error: cannot
send/recv

[Parent 4099] WARNING: pipe error (47): Connection reset by peer: file
/var/tmp/portage/www-client/firefox-52.8.0/work/firefox-52.8.0esr/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
line 322
[Parent 4099] WARNING: pipe error (49): Connection reset by peer: file
/var/tmp/portage/www-client/firefox-52.8.0/work/firefox-52.8.0esr/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
line 322

###!!! [Parent][MessageChannel] Error:
(msgtype=0x2C0083,name=PBrowser::Msg_Destroy) Channel error: cannot
send/recv

tabs.onUpdated event fired after context unloaded.
tabs.onUpdated event fired after context unloaded.
tabs.onUpdated event fired after context unloaded.
...

As to the Qupzilla, it crashes on the page https://www.privat24.ua/#login
completely, with the following messages sent to terminal:

[4376:4387:0727/105105.178569:ERROR:nss_ocsp.cc(591)] No
URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[4376:4387:0727/105105.178676:ERROR:nss_ocsp.cc(591)] No
URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[4376:4387:0727/105105.178734:ERROR:nss_ocsp.cc(591)] No
URLRequestContext for NSS HTTP handler. host: crl4.digicert.com
[4376:4387:0727/105105.182973:ERROR:nss_ocsp.cc(591)] No
URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[4376:4387:0727/105105.183033:ERROR:nss_ocsp.cc(591)] No
URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[4376:4387:0727/105105.183086:ERROR:nss_ocsp.cc(591)] No
URLRequestContext for NSS HTTP handler. host: crl4.digicert.com
r300 FP: Compiler Error:
/var/tmp/portage/media-libs/mesa-17.3.9/work/mesa-17.3.9/src/gallium/drivers/r300/compiler/r300_fragprog_emit.c::translate_rgb_opcode():
translate_rgb_opcode: Unknown opcode DDY
Using a dummy shader instead.
QupZilla: Crashed :( Saving backtrace in
/home/user/.config/qupzilla/crashlog ...
Backtrace successfully saved in
/home/user/.config/qupzilla/crashlog/Crash-2018-07-27T10:51:11.txt

The mentioned above crashlog file contains only the following:

Time: Fri Jul 27 10:51:11 2018
Qt version: 5.9.6 (compiled with 5.9.4)
QupZilla version: 2.2.5
Rendering engine: QtWebEngine

============== BACKTRACE ==============
#0: qupzilla(+0x355b) [0x55691e37055b]
#1: /lib64/libc.so.6(+0x35c60) [0x7f3a568c3c60]
#2: [0x7f3a3c18d2c9]

Strange enough, but on the old Gentoo system Firefox does not crash on
the said www-pages.

I initially thought that all that because
I have set -consolekit and -policykit use
flags in my /etc/portage/make.conf on my
new Gentoo system but unsetting them
does not lead to any recompilation while running
# emerge --update --deep --with-bdeps=y --newuse --backtrack=100 --ask world

Any thoughts about this?
Mick
2018-07-27 09:50:01 UTC
Permalink
Post by gevisz
I have two Gentoo systems on the same AMD Athlon 64 X2 computer.
The old one was installed in July 2013 with
default/linux/amd64/13.0/desktop/gnome (stable)
profile and was updated till the middle of
July 2017. Initially it hosted Gnome2
but later I have switched to XFCE4.
The new one was installed in January-February 2018
with default/linux/amd64/17.0/desktop (stable)
profile and was last updated yesterday. From the
very beginning it hosted no DE, only Awesome WM
and dbus.
The home directory is the same and still remembers
Ubuntu 6.04 installation in 2006.
On the old system, I had the problem that chromium
very often (but not always!) asked me for some
(keyring?) password when I opened a new www-page.
Recompilation of it with different user flags did not help.
Go to:

chrome://settings/passwords

Then disable "Offer to save passwords". It should not ask you to save
passwords thereafter.
Post by gevisz
I thought that that was because of the gnome-keyring,
consolekit or policykit packages but without any proof.
From what I understand Chrome/ium will ask the desktop password manager to
handle the saving of website passwords.

Policykit/polkit provides a centralised mechanism for non-privileged processes
to communicate with privileged ones; e.g. when a plain user wants to
hibernate/shutdown, disable NICs, etc.

https://lwn.net/Articles/258592/

Consolekit tracks user sessions and allows switching between users on the same
PC without logging out. As far as I know with the switch to systemd and its
built-in seat/user/session management mechanisms Consolekit is no longer
maintained.
Post by gevisz
So, while installing the new Gentoo system, I decided
to avoid installing any package that needs gnome-keyring,
consolekit or policykit packages.
I think you shouldn't have needed to do all this.
Post by gevisz
I have also set -pam -consolekit and -policykit in my
/etc/portage/make.conf
PAM is used to separate applications from the underlying authentication
mechanisms. It checks OS user/account/passwd/session authentications when
required by applications. This is the backbone of managing Linux
authentications today, although some applications retain their own application
level authentication mechanism (e.g. SSH).

I don't think setting USE="-pam" is advisable for most dekstop use cases.
Post by gevisz
Chromium indeed never asked me for the mentioned
above password on the new Gentoo system.
Firefox and Qupzilla both crash on some (login) www-pages.
Namely, Firefox shows the "Gah. Your tab just crashed"
when I try to log into my Yahoo e-mail account.
This happens only after entering login and password,
so not good enough to reproduce.
However, it shows the same message just after staying
about 3-5 seconds on the following internet banking
login page: https://www.privat24.ua/#login
No login or password needed. :)
The last error messages sent to terminal by FF while I
The server disconnected you.
Post by gevisz
file
/var/tmp/portage/www-client/firefox-52.8.0/work/firefox-52.8.0esr/ipc/chromi
um/src/chrome/common/ipc_channel_posix.cc, line 322
I'm not sure if your firefox build is the same like shown here, but line 322
shows a I/O message loop where it checks if a connection is running so that it
can respond.

The page in question pops up a couple of things, after loading the initial
page, including geolocation. It may have something to do with this.
Post by gevisz
(msgtype=0x2C0083,name=PBrowser::Msg_Destroy) Channel error: cannot
send/recv
It seems the connection has been reset by the server, two processes running on
your browser using IPC can't go anywhere and are torn down, but I'm no
developer to know for sure.
Post by gevisz
As to the Qupzilla, it crashes on the page https://www.privat24.ua/#login
[4376:4387:0727/105105.178569:ERROR:nss_ocsp.cc(591)] No
URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[snip ...]

The browser is trying to check ocsp.digicert.com for the validity of the
certificate, but there is some error with the URL. Then (I'm guessing)
there's some pop up in the browser to inform you of this error, which causes a
Post by gevisz
/var/tmp/portage/media-libs/mesa-17.3.9/work/mesa-17.3.9/src/gallium/drivers
translate_rgb_opcode: Unknown opcode DDY
Using a dummy shader instead.
QupZilla: Crashed :( Saving backtrace in
/home/user/.config/qupzilla/crashlog ...
Backtrace successfully saved in
/home/user/.config/qupzilla/crashlog/Crash-2018-07-27T10:51:11.txt
Time: Fri Jul 27 10:51:11 2018
Qt version: 5.9.6 (compiled with 5.9.4)
QupZilla version: 2.2.5
Rendering engine: QtWebEngine
============== BACKTRACE ==============
#0: qupzilla(+0x355b) [0x55691e37055b]
#1: /lib64/libc.so.6(+0x35c60) [0x7f3a568c3c60]
#2: [0x7f3a3c18d2c9]
I wouldn't know why the rendered content causes a mesa fault with the gallium
driver, which brings down the browser. Are you running the browser in a
container? Does it have enough memory allocated to it?
Post by gevisz
Strange enough, but on the old Gentoo system Firefox does not crash on
the said www-pages.
I initially thought that all that because
I have set -consolekit and -policykit use
flags in my /etc/portage/make.conf on my
new Gentoo system but unsetting them
does not lead to any recompilation while running
# emerge --update --deep --with-bdeps=y --newuse --backtrack=100 --ask world
Any thoughts about this?
--
Regards,
Mick
gevisz
2018-07-27 10:50:01 UTC
Permalink
Post by Mick
Post by gevisz
I have two Gentoo systems on the same AMD Athlon 64 X2 computer.
The old one was installed in July 2013 with
default/linux/amd64/13.0/desktop/gnome (stable)
profile and was updated till the middle of
July 2017. Initially it hosted Gnome2
but later I have switched to XFCE4.
The new one was installed in January-February 2018
with default/linux/amd64/17.0/desktop (stable)
profile and was last updated yesterday. From the
very beginning it hosted no DE, only Awesome WM
and dbus.
The home directory is the same and still remembers
Ubuntu 6.04 installation in 2006.
On the old system, I had the problem that chromium
very often (but not always!) asked me for some
(keyring?) password when I opened a new www-page.
Recompilation of it with different user flags did not help.
chrome://settings/passwords
Then disable "Offer to save passwords". It should not ask
you to save passwords thereafter.
Thank you for your reply.

Chromium asked for a password to keyring or something like
that and did it on opening almost any page, even that that
definitely did not need any password authentication.

So, it was something else than just saving password for pages.

But it does not matter much now because I currently do not
use Chromium any more because it compiles more than 26 hours
on my computer.
Post by Mick
Post by gevisz
I thought that that was because of the gnome-keyring,
consolekit or policykit packages but without any proof.
From what I understand Chrome/ium will ask the desktop
password manager to handle the saving of website passwords.
I guess he [Chromium] asked me for the password from
a password manager I may be used in previous intallation
of Ubuntu 5 or 10 years ago. However, I never give him
that password (because did not remember any such
password or even when I could create it in the past), so
he asked almost every time he opened new page. :)
Post by Mick
Policykit/polkit provides a centralised mechanism for
non-privileged processes to communicate with privileged
ones; e.g. when a plain user wants to hibernate/shutdown,
disable NICs, etc.
https://lwn.net/Articles/258592/
Consolekit tracks user sessions and allows switching between
users on the same PC without logging out.
I am using my computer alone, so I guess that I do not need it.
Post by Mick
As far as I know with the switch to systemd and its built-in
seat/user/session management mechanisms Consolekit
is no longer maintained.
I do not use systemd.
Post by Mick
Post by gevisz
So, while installing the new Gentoo system, I decided
to avoid installing any package that needs gnome-keyring,
consolekit or policykit packages.
I think you shouldn't have needed to do all this.
Post by gevisz
I have also set -pam -consolekit and -policykit in my
/etc/portage/make.conf
PAM is used to separate applications from the underlying
authentication mechanisms. It checks OS user/account/passwd/session
authentications when required by applications. This is the backbone
of managing Linux authentications today, although some applications
retain their own application level authentication mechanism (e.g. SSH).
So, do you think that global -pam use flag can cause Firefox
and QupZilla to crash on loging web-pages?
Post by Mick
I don't think setting USE="-pam" is advisable for most dekstop use cases.
Post by gevisz
Chromium indeed never asked me for the mentioned
above password on the new Gentoo system.
Firefox and Qupzilla both crash on some (login) www-pages.
Namely, Firefox shows the "Gah. Your tab just crashed"
when I try to log into my Yahoo e-mail account.
This happens only after entering login and password,
so not good enough to reproduce.
However, it shows the same message just after staying
about 3-5 seconds on the following internet banking
login page: https://www.privat24.ua/#login
No login or password needed. :)
The last error messages sent to terminal by FF while I
The server disconnected you.
Post by gevisz
file
/var/tmp/portage/www-client/firefox-52.8.0/work/firefox-52.8.0esr/ipc/chromi
um/src/chrome/common/ipc_channel_posix.cc, line 322
I'm not sure if your firefox build is the same like shown here,
Yes, the same.
Post by Mick
but line 322 shows a I/O message loop where it checks if a connection
is running so that it can respond.
The page in question pops up a couple of things, after loading the initial
page, including geolocation.
Geolocation frame pops up, but on the old Gentoo system
it does not lead to the tab crash.
Post by Mick
It may have something to do with this.
Post by gevisz
(msgtype=0x2C0083,name=PBrowser::Msg_Destroy) Channel error: cannot
send/recv
It seems the connection has been reset by the server, two processes running on
your browser using IPC can't go anywhere and are torn down, but I'm no
developer to know for sure.
Post by gevisz
As to the Qupzilla, it crashes on the page https://www.privat24.ua/#login
[4376:4387:0727/105105.178569:ERROR:nss_ocsp.cc(591)] No
URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[snip ...]
The browser is trying to check ocsp.digicert.com for the validity of the
certificate, but there is some error with the URL. Then (I'm guessing)
there's some pop up in the browser to inform you of this error, which causes a
Post by gevisz
/var/tmp/portage/media-libs/mesa-17.3.9/work/mesa-17.3.9/src/gallium/drivers
translate_rgb_opcode: Unknown opcode DDY
Using a dummy shader instead.
QupZilla: Crashed :( Saving backtrace in
/home/user/.config/qupzilla/crashlog ...
Backtrace successfully saved in
/home/user/.config/qupzilla/crashlog/Crash-2018-07-27T10:51:11.txt
Time: Fri Jul 27 10:51:11 2018
Qt version: 5.9.6 (compiled with 5.9.4)
QupZilla version: 2.2.5
Rendering engine: QtWebEngine
============== BACKTRACE ==============
#0: qupzilla(+0x355b) [0x55691e37055b]
#1: /lib64/libc.so.6(+0x35c60) [0x7f3a568c3c60]
#2: [0x7f3a3c18d2c9]
I wouldn't know why the rendered content causes a mesa fault with the gallium
driver, which brings down the browser. Are you running the browser in a
container? Does it have enough memory allocated to it?
No, I do not run browser in a container. There is also plenty of memory.
Here is the output from top with FF running:
$ top

top - 13:02:44 up 2:50, 1 user, load average: 0.16, 0.26, 0.35
Tasks: 95 total, 1 running, 94 sleeping, 0 stopped, 0 zombie
%Cpu(s): 3.2 us, 6.5 sy, 0.0 ni, 90.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
MiB Mem : 7721.3 total, 5504.1 free, 614.2 used, 1603.1 buff/cache
MiB Swap: 12000.0 total, 12000.0 free, 0.0 used. 6946.5 avail Mem

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+
COMMAND
3648 root 20 0 450736 66136 46024 S 13.3 0.8 4:40.45 X
5463 gevis 20 0 1957104 401300 121472 S 6.7 5.1 1:04.86
Web Content
1 root 20 0 4328 1588 1488 S 0.0 0.0 0:01.22
init
2 root 20 0 0 0 0 S 0.0 0.0 0:00.00
kthreadd
3 root 20 0 0 0 0 S 0.0 0.0 0:00.03
ksoftirqd/0
5 root 0 -20 0 0 0 S 0.0 0.0 0:00.00
kworker/0:0H
Post by Mick
Post by gevisz
Strange enough, but on the old Gentoo system Firefox does not crash on
the said www-pages.
I initially thought that all that because
I have set -consolekit and -policykit use
flags in my /etc/portage/make.conf on my
new Gentoo system but unsetting them
does not lead to any recompilation while running
# emerge --update --deep --with-bdeps=y --newuse --backtrack=100 --ask world
Any thoughts about this?
Mick
2018-07-27 11:00:01 UTC
Permalink
Post by gevisz
Post by Mick
PAM is used to separate applications from the underlying
authentication mechanisms. It checks OS user/account/passwd/session
authentications when required by applications. This is the backbone
of managing Linux authentications today, although some applications
retain their own application level authentication mechanism (e.g. SSH).
So, do you think that global -pam use flag can cause Firefox
and QupZilla to crash on loging web-pages?
You can run them with strace to see if they are trying to access any pam
modules, but I would think it unlikely.

I bet this is something to do with the graphics drivers. Later versions of
browsers are heavy on hardware acceleration and can stress some graphics
drivers causing crashes like this. Geolocation and other pop ups use the GPU
to create rendering effects and this could be the cause of the crash.

PS. My wife's FF started crashing recently whenever she closes a single tab -
but not every time. :-/
--
Regards,
Mick
gevisz
2018-07-27 11:20:01 UTC
Permalink
Post by Mick
Post by gevisz
Post by Mick
PAM is used to separate applications from the underlying
authentication mechanisms. It checks OS user/account/passwd/session
authentications when required by applications. This is the backbone
of managing Linux authentications today, although some applications
retain their own application level authentication mechanism (e.g. SSH).
So, do you think that global -pam use flag can cause Firefox
and QupZilla to crash on loging web-pages?
You can run them with strace to see if they are trying to access any pam
modules, but I would think it unlikely.
Thank you for the tip. I will try to use strace after reading about it.

However, currently I already deleted grobal -pam use flag and
started to update world with the new settings. Some new packages
are currently installing and some other are recompiling.
Post by Mick
I bet this is something to do with the graphics drivers. Later versions of
browsers are heavy on hardware acceleration and can stress some graphics
drivers causing crashes like this. Geolocation and other pop ups use the GPU
to create rendering effects and this could be the cause of the crash.
I doubt this because the same works on old Gentoo intallation on
the same computer. But I can not be sure, of course. :)
gevisz
2018-07-27 12:50:01 UTC
Permalink
Post by gevisz
Post by Mick
Post by gevisz
Post by Mick
PAM is used to separate applications from the underlying
authentication mechanisms. It checks OS user/account/passwd/session
authentications when required by applications. This is the backbone
of managing Linux authentications today, although some applications
retain their own application level authentication mechanism (e.g. SSH).
So, do you think that global -pam use flag can cause Firefox
and QupZilla to crash on loging web-pages?
You can run them with strace to see if they are trying to access any pam
modules, but I would think it unlikely.
Thank you for the tip. I will try to use strace after reading about it.
However, currently I already deleted grobal -pam use flag and
started to update world with the new settings. Some new packages
are currently installing and some other are recompiling.
Updating world without global -pam, -polkit and -consolekit use flags
in /etc/portage/make.conf have not changed the behaviour of Fireforx
described above: it is still cannot display the page https://www.privat24.ua/
and shows "Gah. Your tab just crashed." message.

So, I will probably revert changes tomorrow.

Playing with strace has been put on todo list.

Any more adeas?
gevisz
2018-07-27 13:10:02 UTC
Permalink
Post by gevisz
Updating world without global -pam, -polkit and -consolekit use flags
in /etc/portage/make.conf have not changed the behaviour of Fireforx
described above: it is still cannot display the page https://www.privat24.ua/
and shows "Gah. Your tab just crashed." message.
So, I will probably revert changes tomorrow.
Playing with strace has been put on todo list.
Last lines of the log file after runnig the following command

$ strace -o strace.log qupzilla https://www.privat24.ua/
QupZilla: 0 extensions loaded
[15707:15725:0727/155144.939329:ERROR:nss_util.cc(808)] After loading
Root Certs, loaded==false: NSS error code: -8018
[15707:15719:0727/155145.900259:ERROR:nss_ocsp.cc(591)] No
URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[15707:15719:0727/155145.900327:ERROR:nss_ocsp.cc(591)] No
URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[15707:15719:0727/155145.900384:ERROR:nss_ocsp.cc(591)] No
URLRequestContext for NSS HTTP handler. host: crl4.digicert.com
[15707:15719:0727/155145.904387:ERROR:nss_ocsp.cc(591)] No
URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[15707:15719:0727/155145.904448:ERROR:nss_ocsp.cc(591)] No
URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[15707:15719:0727/155145.904496:ERROR:nss_ocsp.cc(591)] No
URLRequestContext for NSS HTTP handler. host: crl4.digicert.com
r300 FP: Compiler Error:
/var/tmp/portage/media-libs/mesa-17.3.9/work/mesa-17.3.9/src/gallium/drivers/r300/compiler/r300_fragprog_emit.c::translate_rgb_opcode():
translate_rgb_opcode: Unknown opcode DDY
Using a dummy shader instead.
QupZilla: Crashed :( Saving backtrace in
/home/gevis/.config/qupzilla/crashlog ...
Backtrace successfully saved in
/home/gevis/.config/qupzilla/crashlog/Crash-2018-07-27T15:51:49.txt
zsh: abort strace -o strace.log qupzilla https://www.privat24.ua/

are the following:

read(5, "\1\0\0\0\0\0\0\0", 16) = 8
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1166, tv_nsec=988321461}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1166, tv_nsec=988368394}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1166, tv_nsec=988415817}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1166, tv_nsec=988467639}) = 0
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=12,
events=POLLIN}, {fd=44, events=POLLIN}], 4, 0) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1166, tv_nsec=988568839}) = 0
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=12,
events=POLLIN}, {fd=44, events=POLLIN}], 4, 0) = 1 ([{fd=5,
revents=POLLIN}])
read(5, "\1\0\0\0\0\0\0\0", 16) = 8
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="&\0\2\0y\2\0\0", iov_len=8}], 1) = 8
futex(0x55f78fcb7c08, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x55f78fcb7c08, FUTEX_WAKE_PRIVATE, 1) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1166, tv_nsec=990082928}) = 0
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="\231\7\5\0\21\0\300\1\1\0\0\0\1\0\0\0\30\0\0\0",
iov_len=20}, {iov_base=NULL, iov_len=0}, {iov_base="", iov_len=0}], 3)
= 20
futex(0x55f78fcb7c08, FUTEX_WAKE_PRIVATE, 1) = 1
ioctl(8, DRM_IOCTL_RADEON_GEM_CREATE, 0x7ffd31773080) = 0
ioctl(8, DRM_IOCTL_RADEON_GEM_SET_TILING, 0x7ffd3177311c) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1166, tv_nsec=995358529}) = 0
ioctl(8, DRM_IOCTL_RADEON_GEM_WAIT_IDLE, 0x7ffd31773250) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1166, tv_nsec=995480262}) = 0
ioctl(8, DRM_IOCTL_RADEON_GEM_MMAP, 0x7ffd31773280) = 0
mmap(NULL, 6868992, PROT_READ|PROT_WRITE, MAP_SHARED, 8, 0x1073e4000)
= 0x7f22f5850000
futex(0x55f78fd2d4f4, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x55f78fd2d4a0, FUTEX_WAKE_PRIVATE, 1) = 1
munmap(0x7f22f5850000, 6868992) = 0
ioctl(8, DRM_IOCTL_GEM_CLOSE, 0x7ffd31773358) = 0
futex(0x55f78fe276a8, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x55f78fe276a8, FUTEX_WAIT_PRIVATE, 2, NULL) = 0
futex(0x55f78fe276a8, FUTEX_WAKE_PRIVATE, 1) = 0
ioctl(8, DRM_IOCTL_RADEON_GEM_WAIT_IDLE, 0x7ffd31773900) = 0
ioctl(8, DRM_IOCTL_GEM_CLOSE, 0x7ffd317738d8) = 0
ioctl(8, DRM_IOCTL_RADEON_GEM_CREATE, 0x7ffd317737a0) = 0
futex(0x55f78fd2d4f4, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x55f78fd2d4a0, FUTEX_WAKE_PRIVATE, 1) = 1
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="\231\10\10\0\21\0\300\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
iov_len=32}], 1) = 32
futex(0x55f78fcb7c08, FUTEX_WAKE_PRIVATE, 1) = 1
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="+\7\1\0", iov_len=4}, {iov_base=NULL,
iov_len=0}, {iov_base="", iov_len=0}], 3) = 4
futex(0x55f78fcb7c08, FUTEX_WAKE_PRIVATE, 1) = 1
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=5347019}) = 0
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=12,
events=POLLIN}, {fd=44, events=POLLIN}], 4, 0) = 1 ([{fd=5,
revents=POLLIN}])
read(5, "\2\0\0\0\0\0\0\0", 16) = 8
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=5547952}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=5618352}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=5668708}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=5806085}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=7155908}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=7222397}) = 0
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=7358797}) = 0
write(40, "\0", 1) = 1
futex(0x7f236699fae8, FUTEX_WAKE_PRIVATE, 1) = 1
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=7882886}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=7953775}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=8022708}) = 0
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=12,
events=POLLIN}, {fd=44, events=POLLIN}], 4, 0) = 1 ([{fd=5,
revents=POLLIN}])
read(5, "\1\0\0\0\0\0\0\0", 16) = 8
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=8261775}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=8308219}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=8355152}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=8406975}) = 0
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=12,
events=POLLIN}, {fd=44, events=POLLIN}], 4, 14) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=22634621}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=22684488}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=22725554}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=22754888}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=22785199}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=22815999}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=22844354}) = 0
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=22923065}) = 0
write(40, "\0", 1) = 1
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=22989554}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=23035510}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=23065332}) = 0
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=12,
events=POLLIN}, {fd=44, events=POLLIN}], 4, 0) = 1 ([{fd=5,
revents=POLLIN}])
read(5, "\1\0\0\0\0\0\0\0", 16) = 8
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=23395821}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=23425154}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=23454977}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=23491154}) = 0
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=12,
events=POLLIN}, {fd=44, events=POLLIN}], 4, 14) = 1 ([{fd=5,
revents=POLLIN}])
read(5, "\1\0\0\0\0\0\0\0", 16) = 8
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=33682045}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=33759289}) = 0
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=12,
events=POLLIN}, {fd=44, events=POLLIN}], 4, 4) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=37929512}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=37970578}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=38046845}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=38078623}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=38108934}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=38140223}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=38169067}) = 0
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=38250712}) = 0
write(40, "\0", 1) = 1
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=38318178}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=38349956}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=38381245}) = 0
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=12,
events=POLLIN}, {fd=44, events=POLLIN}], 4, 0) = 1 ([{fd=5,
revents=POLLIN}])
read(5, "\1\0\0\0\0\0\0\0", 16) = 8
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=38747912}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=38777734}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=38807067}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=38842267}) = 0
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=12,
events=POLLIN}, {fd=44, events=POLLIN}], 4, 12) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=50991158}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=51038091}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=51084047}) = 0
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=12,
events=POLLIN}, {fd=44, events=POLLIN}], 4, 3) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=54251069}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=54281380}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=54319514}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=54348847}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=54378180}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=54408492}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=54436358}) = 0
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=54512625}) = 0
write(40, "\0", 1) = 1
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=54578136}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=54609914}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=54638758}) = 0
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=12,
events=POLLIN}, {fd=44, events=POLLIN}], 4, 0) = 1 ([{fd=5,
revents=POLLIN}])
read(5, "\1\0\0\0\0\0\0\0", 16) = 8
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=54935514}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=54964358}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=54994181}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=55047958}) = 0
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=12,
events=POLLIN}, {fd=44, events=POLLIN}], 4, 5) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=60192048}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=60224803}) = 0
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=12,
events=POLLIN}, {fd=44, events=POLLIN}], 4, 0) = 1 ([{fd=5,
revents=POLLIN}])
read(5, "\1\0\0\0\0\0\0\0", 16) = 8
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="&\0\2\0y\2\0\0", iov_len=8}], 1) = 8
futex(0x55f78fcb7c08, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x55f78fcb7c08, FUTEX_WAKE_PRIVATE, 1) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=61487115}) = 0
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="\231\7\5\0\21\0\300\1\1\0\0\0\1\0\0\0\30\0\0\0",
iov_len=20}, {iov_base=NULL, iov_len=0}, {iov_base="", iov_len=0}], 3)
= 20
futex(0x55f78fcb7c08, FUTEX_WAKE_PRIVATE, 1) = 1
ioctl(8, DRM_IOCTL_RADEON_GEM_CREATE, 0x7ffd31773080) = 0
ioctl(8, DRM_IOCTL_RADEON_GEM_SET_TILING, 0x7ffd3177311c) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=68455249}) = 0
ioctl(8, DRM_IOCTL_RADEON_GEM_WAIT_IDLE, 0x7ffd31773250) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=68524671}) = 0
ioctl(8, DRM_IOCTL_RADEON_GEM_MMAP, 0x7ffd31773280) = 0
mmap(NULL, 6868992, PROT_READ|PROT_WRITE, MAP_SHARED, 8, 0x107616000)
= 0x7f22f5650000
+++ killed by SIGABRT +++
Mick
2018-07-27 15:40:02 UTC
Permalink
Post by gevisz
Post by gevisz
Updating world without global -pam, -polkit and -consolekit use flags
in /etc/portage/make.conf have not changed the behaviour of Fireforx
described above: it is still cannot display the page
https://www.privat24.ua/ and shows "Gah. Your tab just crashed." message.
So, I will probably revert changes tomorrow.
Playing with strace has been put on todo list.
Last lines of the log file after runnig the following command
$ strace -o strace.log qupzilla https://www.privat24.ua/
QupZilla: 0 extensions loaded
[15707:15725:0727/155144.939329:ERROR:nss_util.cc(808)] After loading
Root Certs, loaded==false: NSS error code: -8018
[15707:15719:0727/155145.900259:ERROR:nss_ocsp.cc(591)] No
URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
Mozilla is using libnss to check the validity of the website certificate with
the OCSP of the CA issuer of the certificate (digicert.com). For some reason
it seems the connection is interrupted. See lines 605 to 621 here:

https://code.woboq.org/qt5/qtwebengine/src/3rdparty/chromium/net/cert_net/
nss_ocsp.cc.html

The connection may be interrupted because the browser/tab crashes (see below).
Post by gevisz
/var/tmp/portage/media-libs/mesa-17.3.9/work/mesa-17.3.9/src/gallium/drivers
translate_rgb_opcode: Unknown opcode DDY
Using a dummy shader instead.
QupZilla: Crashed :( Saving backtrace in
/home/gevis/.config/qupzilla/crashlog ...
Backtrace successfully saved in
/home/gevis/.config/qupzilla/crashlog/Crash-2018-07-27T15:51:49.txt
zsh: abort strace -o strace.log qupzilla https://www.privat24.ua/
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=68524671}) = 0
ioctl(8, DRM_IOCTL_RADEON_GEM_MMAP, 0x7ffd31773280) = 0
mmap(NULL, 6868992, PROT_READ|PROT_WRITE, MAP_SHARED, 8, 0x107616000)
= 0x7f22f5650000
+++ killed by SIGABRT +++
This looks like a radeon video driver problem. You could go into a loop of
rebuilding xorg, mesa, dev-libs/nss, what-ever and see if things improve, or
you could wait for/keyword later versions of these packages.

Alternatively, you could try reporting this to the application devs and see
what they say.
--
Regards,
Mick
gevisz
2018-07-27 19:00:01 UTC
Permalink
Post by Mick
Post by gevisz
Post by gevisz
Updating world without global -pam, -polkit and -consolekit use flags
in /etc/portage/make.conf have not changed the behaviour of Fireforx
described above: it is still cannot display the page
https://www.privat24.ua/ and shows "Gah. Your tab just crashed." message.
So, I will probably revert changes tomorrow.
Playing with strace has been put on todo list.
Last lines of the log file after runnig the following command
$ strace -o strace.log qupzilla https://www.privat24.ua/
QupZilla: 0 extensions loaded
[15707:15725:0727/155144.939329:ERROR:nss_util.cc(808)] After loading
Root Certs, loaded==false: NSS error code: -8018
[15707:15719:0727/155145.900259:ERROR:nss_ocsp.cc(591)] No
URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
Mozilla is using libnss to check the validity of the website certificate with
the OCSP of the CA issuer of the certificate (digicert.com). For some reason
https://code.woboq.org/qt5/qtwebengine/src/3rdparty/chromium/net/cert_net/
nss_ocsp.cc.html
The connection may be interrupted because the browser/tab crashes (see below).
Post by gevisz
/var/tmp/portage/media-libs/mesa-17.3.9/work/mesa-17.3.9/src/gallium/drivers
translate_rgb_opcode: Unknown opcode DDY
Using a dummy shader instead.
QupZilla: Crashed :( Saving backtrace in
/home/gevis/.config/qupzilla/crashlog ...
Backtrace successfully saved in
/home/gevis/.config/qupzilla/crashlog/Crash-2018-07-27T15:51:49.txt
zsh: abort strace -o strace.log qupzilla https://www.privat24.ua/
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=68524671}) = 0
ioctl(8, DRM_IOCTL_RADEON_GEM_MMAP, 0x7ffd31773280) = 0
mmap(NULL, 6868992, PROT_READ|PROT_WRITE, MAP_SHARED, 8, 0x107616000)
= 0x7f22f5650000
+++ killed by SIGABRT +++
This looks like a radeon video driver problem. You could go into a loop of
rebuilding xorg, mesa, dev-libs/nss, what-ever and see if things improve, or
you could wait for/keyword later versions of these packages.
Thank you for the tip. In this case, I should first try reconfigure the kernel.
Post by Mick
Alternatively, you could try reporting this to the application devs and see
what they say.
Do you mean developpers of FF/QZ?
Mick
2018-07-27 20:10:02 UTC
Permalink
Post by gevisz
Post by Mick
Post by gevisz
Post by gevisz
Updating world without global -pam, -polkit and -consolekit use flags
in /etc/portage/make.conf have not changed the behaviour of Fireforx
described above: it is still cannot display the page
https://www.privat24.ua/ and shows "Gah. Your tab just crashed." message.
So, I will probably revert changes tomorrow.
Playing with strace has been put on todo list.
Last lines of the log file after runnig the following command
$ strace -o strace.log qupzilla https://www.privat24.ua/
QupZilla: 0 extensions loaded
[15707:15725:0727/155144.939329:ERROR:nss_util.cc(808)] After loading
Root Certs, loaded==false: NSS error code: -8018
[15707:15719:0727/155145.900259:ERROR:nss_ocsp.cc(591)] No
URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
Mozilla is using libnss to check the validity of the website certificate
with the OCSP of the CA issuer of the certificate (digicert.com). For
some reason it seems the connection is interrupted. See lines 605 to 621
https://code.woboq.org/qt5/qtwebengine/src/3rdparty/chromium/net/cert_net/
nss_ocsp.cc.html
The connection may be interrupted because the browser/tab crashes (see
below).>
Post by gevisz
/var/tmp/portage/media-libs/mesa-17.3.9/work/mesa-17.3.9/src/gallium/driv
translate_rgb_opcode: Unknown opcode DDY
Using a dummy shader instead.
QupZilla: Crashed :( Saving backtrace in
/home/gevis/.config/qupzilla/crashlog ...
Backtrace successfully saved in
/home/gevis/.config/qupzilla/crashlog/Crash-2018-07-27T15:51:49.txt
zsh: abort strace -o strace.log qupzilla https://www.privat24.ua/
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=68524671}) = 0
ioctl(8, DRM_IOCTL_RADEON_GEM_MMAP, 0x7ffd31773280) = 0
mmap(NULL, 6868992, PROT_READ|PROT_WRITE, MAP_SHARED, 8, 0x107616000)
= 0x7f22f5650000
+++ killed by SIGABRT +++
This looks like a radeon video driver problem. You could go into a loop of
rebuilding xorg, mesa, dev-libs/nss, what-ever and see if things improve,
or you could wait for/keyword later versions of these packages.
Thank you for the tip. In this case, I should first try reconfigure the kernel.
Post by Mick
Alternatively, you could try reporting this to the application devs and see
what they say.
Do you mean developpers of FF/QZ?
Yes, although unless this is a known bug they may point you to the devs of the
radeon drivers. I've been around this loop a couple of times (sigh ...)
--
Regards,
Mick
gevisz
2018-07-28 12:30:01 UTC
Permalink
Post by Mick
Post by gevisz
Post by Mick
Post by gevisz
Post by gevisz
Updating world without global -pam, -polkit and -consolekit use flags
in /etc/portage/make.conf have not changed the behaviour of Fireforx
described above: it is still cannot display the page
https://www.privat24.ua/ and shows "Gah. Your tab just crashed." message.
So, I will probably revert changes tomorrow.
Playing with strace has been put on todo list.
Last lines of the log file after runnig the following command
$ strace -o strace.log qupzilla https://www.privat24.ua/
QupZilla: 0 extensions loaded
[15707:15725:0727/155144.939329:ERROR:nss_util.cc(808)] After loading
Root Certs, loaded==false: NSS error code: -8018
[15707:15719:0727/155145.900259:ERROR:nss_ocsp.cc(591)] No
URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
Mozilla is using libnss to check the validity of the website certificate
with the OCSP of the CA issuer of the certificate (digicert.com). For
some reason it seems the connection is interrupted. See lines 605 to 621
https://code.woboq.org/qt5/qtwebengine/src/3rdparty/chromium/net/cert_net/
nss_ocsp.cc.html
The connection may be interrupted because the browser/tab crashes (see
below).>
Post by gevisz
/var/tmp/portage/media-libs/mesa-17.3.9/work/mesa-17.3.9/src/gallium/driv
translate_rgb_opcode: Unknown opcode DDY
Using a dummy shader instead.
QupZilla: Crashed :( Saving backtrace in
/home/gevis/.config/qupzilla/crashlog ...
Backtrace successfully saved in
/home/gevis/.config/qupzilla/crashlog/Crash-2018-07-27T15:51:49.txt
zsh: abort strace -o strace.log qupzilla https://www.privat24.ua/
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=68524671}) = 0
ioctl(8, DRM_IOCTL_RADEON_GEM_MMAP, 0x7ffd31773280) = 0
mmap(NULL, 6868992, PROT_READ|PROT_WRITE, MAP_SHARED, 8, 0x107616000)
= 0x7f22f5650000
+++ killed by SIGABRT +++
This looks like a radeon video driver problem. You could go into a loop of
rebuilding xorg, mesa, dev-libs/nss, what-ever and see if things improve,
or you could wait for/keyword later versions of these packages.
Thank you for the tip. In this case, I should first try reconfigure the kernel.
Post by Mick
Alternatively, you could try reporting this to the application devs and see
what they say.
Do you mean developpers of FF/QZ?
Yes, although unless this is a known bug they may point you to the devs of the
radeon drivers. I've been around this loop a couple of times (sigh ...)
Ok. Thank you.

It even more strengthens my impression than I should first
play with reconfiguring the kernel.

I will do it a bit later, when the summer heat becames more tolerable. :)
gevisz
2018-07-29 20:50:02 UTC
Permalink
Post by gevisz
Post by Mick
Post by gevisz
Post by Mick
Post by gevisz
Post by gevisz
Updating world without global -pam, -polkit and -consolekit use flags
in /etc/portage/make.conf have not changed the behaviour of Fireforx
described above: it is still cannot display the page
https://www.privat24.ua/ and shows "Gah. Your tab just crashed." message.
So, I will probably revert changes tomorrow.
Playing with strace has been put on todo list.
Last lines of the log file after runnig the following command
$ strace -o strace.log qupzilla https://www.privat24.ua/
QupZilla: 0 extensions loaded
[15707:15725:0727/155144.939329:ERROR:nss_util.cc(808)] After loading
Root Certs, loaded==false: NSS error code: -8018
[15707:15719:0727/155145.900259:ERROR:nss_ocsp.cc(591)] No
URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
Mozilla is using libnss to check the validity of the website certificate
with the OCSP of the CA issuer of the certificate (digicert.com). For
some reason it seems the connection is interrupted. See lines 605 to 621
https://code.woboq.org/qt5/qtwebengine/src/3rdparty/chromium/net/cert_net/
nss_ocsp.cc.html
The connection may be interrupted because the browser/tab crashes (see
below).>
Post by gevisz
/var/tmp/portage/media-libs/mesa-17.3.9/work/mesa-17.3.9/src/gallium/driv
translate_rgb_opcode: Unknown opcode DDY
Using a dummy shader instead.
QupZilla: Crashed :( Saving backtrace in
/home/gevis/.config/qupzilla/crashlog ...
Backtrace successfully saved in
/home/gevis/.config/qupzilla/crashlog/Crash-2018-07-27T15:51:49.txt
zsh: abort strace -o strace.log qupzilla https://www.privat24.ua/
clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=68524671}) = 0
ioctl(8, DRM_IOCTL_RADEON_GEM_MMAP, 0x7ffd31773280) = 0
mmap(NULL, 6868992, PROT_READ|PROT_WRITE, MAP_SHARED, 8, 0x107616000)
= 0x7f22f5650000
+++ killed by SIGABRT +++
This looks like a radeon video driver problem. You could go into a loop of
rebuilding xorg, mesa, dev-libs/nss, what-ever and see if things improve,
or you could wait for/keyword later versions of these packages.
Thank you for the tip. In this case, I should first try reconfigure the kernel.
Post by Mick
Alternatively, you could try reporting this to the application devs and see
what they say.
Do you mean developpers of FF/QZ?
Yes, although unless this is a known bug they may point you to the devs of the
radeon drivers. I've been around this loop a couple of times (sigh ...)
Ok. Thank you.
It even more strengthens my impression than I should first
play with reconfiguring the kernel.
I have loaded the new Gentoo system using the kernel from the old one
with no change in Firefox behaviour on https://www.privat24.ua/#login
page: it crashed as was described before.

So, playing with the kernel configuration will not help. :(
Adam Carter
2018-07-31 23:50:02 UTC
Permalink
Post by gevisz
Post by gevisz
It even more strengthens my impression than I should first
play with reconfiguring the kernel.
I have loaded the new Gentoo system using the kernel from the old one
with no change in Firefox behaviour on https://www.privat24.ua/#login
page: it crashed as was described before.
So, playing with the kernel configuration will not help. :(
I think this "This looks like a radeon video driver problem. You could go
into a loop of rebuilding xorg, mesa, dev-libs/nss, what-ever and see if
things improve" is the best suggestion so far.

I would do something like 'emerge -1 xorg-server xorg-drivers
@x11-module-rebuild mesa llvm clang' then restart X and try again.
gevisz
2018-08-01 09:40:01 UTC
Permalink
Post by Adam Carter
Post by gevisz
Post by gevisz
It even more strengthens my impression than I should first
play with reconfiguring the kernel.
I have loaded the new Gentoo system using the kernel from the old one
with no change in Firefox behaviour on https://www.privat24.ua/#login
page: it crashed as was described before.
So, playing with the kernel configuration will not help. :(
I think this "This looks like a radeon video driver problem. You could go
into a loop of rebuilding xorg, mesa, dev-libs/nss, what-ever and see if
things improve" is the best suggestion so far.
I would do something like 'emerge -1 xorg-server xorg-drivers
@x11-module-rebuild mesa llvm clang' then restart X and try again.
Thank you for your reply.

Initially, I understood the above recomendation as the suggestion to
rebuild the packages mentioned above with different use flags.

Do you think that rebuilding them with the same use flags may help?

The said problem appeared just since the intallation of the new
Gentoo system in January-February 2018 and not since changing
the major version of gcc this spring.

P.S. clang is not installed on my Gentoo system at all.
Adam Carter
2018-08-02 00:20:01 UTC
Permalink
Post by gevisz
Post by Adam Carter
I would do something like 'emerge -1 xorg-server xorg-drivers
@x11-module-rebuild mesa llvm clang' then restart X and try again.
Thank you for your reply.
Initially, I understood the above recomendation as the suggestion to
rebuild the packages mentioned above with different use flags.
Do you think that rebuilding them with the same use flags may help?
It can, for example, if the major version of the kernel has changed but you
havent rebuild xorg since (I only recall having this issue once).

If you use newuse and changed-deps with emerge its probably less likely to
find other issues.
Post by gevisz
The said problem appeared just since the intallation of the new
Gentoo system in January-February 2018 and not since changing
the major version of gcc this spring.
P.S. clang is not installed on my Gentoo system at all.
I've checked the dependencies on my system, and firefox is pulling that in
for me, but checking the ebuilds you can see it becomes a dependency from
v60 onwards;

/usr/portage/www-client/firefox $ ls
files/ firefox-52.9.0.ebuild Manifest
firefox-52.6.0.ebuild firefox-60.1.0.ebuild metadata.xml
firefox-52.8.0.ebuild firefox-61.0-r1.ebuild
/usr/portage/www-client/firefox $ grep clang *
grep: files: Is a directory
firefox-60.1.0.ebuild: >=sys-devel/clang-4.0.1
firefox-60.1.0.ebuild: has_version "sys-devel/clang:${LLVM_SLOT}"
firefox-61.0-r1.ebuild: >=sys-devel/clang-4.0.1
firefox-61.0-r1.ebuild: has_version "sys-devel/clang:${LLVM_SLOT}"
/usr/portage/www-client/firefox $
gevisz
2018-08-02 05:20:01 UTC
Permalink
Post by Adam Carter
Post by gevisz
Post by Adam Carter
I would do something like 'emerge -1 xorg-server xorg-drivers
@x11-module-rebuild mesa llvm clang' then restart X and try again.
Thank you for your reply.
Initially, I understood the above recomendation as the suggestion to
rebuild the packages mentioned above with different use flags.
Do you think that rebuilding them with the same use flags may help?
It can, for example, if the major version of the kernel has changed but you
havent rebuild xorg since (I only recall having this issue once).
Ok, thank you. I will try to do it in a two weeks.
(Currently, is still too hot to start so massive recompilation.)
Post by Adam Carter
If you use newuse and changed-deps with emerge its probably less likely to
find other issues.
Post by gevisz
The said problem appeared just since the intallation of the new
Gentoo system in January-February 2018 and not since changing
the major version of gcc this spring.
P.S. clang is not installed on my Gentoo system at all.
I've checked the dependencies on my system, and firefox is pulling that in
for me, but checking the ebuilds you can see it becomes a dependency from
v60 onwards;
/usr/portage/www-client/firefox $ ls
files/ firefox-52.9.0.ebuild Manifest
firefox-52.6.0.ebuild firefox-60.1.0.ebuild metadata.xml
firefox-52.8.0.ebuild firefox-61.0-r1.ebuild
/usr/portage/www-client/firefox $ grep clang *
grep: files: Is a directory
firefox-60.1.0.ebuild: >=sys-devel/clang-4.0.1
firefox-60.1.0.ebuild: has_version "sys-devel/clang:${LLVM_SLOT}"
firefox-61.0-r1.ebuild: >=sys-devel/clang-4.0.1
firefox-61.0-r1.ebuild: has_version "sys-devel/clang:${LLVM_SLOT}"
/usr/portage/www-client/firefox $
Ok, thank you. I still have FF version 5.8.0 (64 bit).
It is the latest stable version on amd64.
gevisz
2018-09-07 15:40:02 UTC
Permalink
Post by Mick
This looks like a radeon video driver problem. You could go into a loop of
rebuilding xorg, mesa, dev-libs/nss, what-ever and see if things improve, or
you could wait for/keyword later versions of these packages.
Just now, I have finished updating my system. It was after a more than
a month of not doing so because of the summer heat. So, there was
a lot of packages to update, including mesa.

After the update, the problem with firefox crashing on privat24.ua
logging page dissappeared. So, it looks like your advise to rebuild
xorg, mesa, etc. was right. Thank you.
Mick
2018-09-07 16:10:01 UTC
Permalink
Post by gevisz
Post by Mick
This looks like a radeon video driver problem. You could go into a loop of
rebuilding xorg, mesa, dev-libs/nss, what-ever and see if things improve,
or you could wait for/keyword later versions of these packages.
Just now, I have finished updating my system. It was after a more than
a month of not doing so because of the summer heat. So, there was
a lot of packages to update, including mesa.
After the update, the problem with firefox crashing on privat24.ua
logging page dissappeared. So, it looks like your advise to rebuild
xorg, mesa, etc. was right. Thank you.
You're welcome. I've been bitten by similar problems in the past and quite
often there is no way out other than reverting an update and waiting for a
later more polished version of a package.

Something else I came across causing FF crashes here, was a bug with profile-
sync-daemon (recent thread of mine refers). I don't know if you use psd, but
I wasn't aware of this psd bug when you posted about your problems. I only
mention it now as another thing to check next time you have FF crashing on
you.
--
Regards,
Mick
gevisz
2018-09-16 07:30:02 UTC
Permalink
Post by Mick
Something else I came across causing FF crashes here, was a bug with profile-
sync-daemon (recent thread of mine refers). I don't know if you use psd, but
I wasn't aware of this psd bug when you posted about your problems. I only
mention it now as another thing to check next time you have FF crashing on
you.
Thank you for additional information.

I have read in this mailing list (may be it was your thread) that using profiles
in firefox is another source of crashes. So, I do not use profiles, and now hope
that it means that I do not use psd as well. :)
Mick
2018-09-16 08:00:02 UTC
Permalink
Post by gevisz
Post by Mick
Something else I came across causing FF crashes here, was a bug with
profile- sync-daemon (recent thread of mine refers). I don't know if you
use psd, but I wasn't aware of this psd bug when you posted about your
problems. I only mention it now as another thing to check next time you
have FF crashing on you.
Thank you for additional information.
I have read in this mailing list (may be it was your thread) that using
profiles in firefox is another source of crashes. So, I do not use
profiles, and now hope that it means that I do not use psd as well. :)
Ah! No, they are too different things.

I have not read anywhere that the use of multiple user profiles causes FF to
crash. Perhaps some addons may do.

The use of psd on the other hand is a useful package, minimising the writing
cycles of the browser's cache to disk. If your PC is running on SDD or hybrid
disks and has enough RAM, then a profile-sync-daemon (when it is not buggy)
should be a good thing.
--
Regards,
Mick
Dale
2018-09-16 08:10:01 UTC
Permalink
Post by Mick
Post by gevisz
Post by Mick
Something else I came across causing FF crashes here, was a bug with
profile- sync-daemon (recent thread of mine refers). I don't know if you
use psd, but I wasn't aware of this psd bug when you posted about your
problems. I only mention it now as another thing to check next time you
have FF crashing on you.
Thank you for additional information.
I have read in this mailing list (may be it was your thread) that using
profiles in firefox is another source of crashes. So, I do not use
profiles, and now hope that it means that I do not use psd as well. :)
Ah! No, they are too different things.
I have not read anywhere that the use of multiple user profiles causes FF to
crash. Perhaps some addons may do.
<<SNIP>>
I have nine Firefox profiles here.  Any problems I have had have turned
out to be a bad add on.  Sometimes I turn off auto update and new
Firefox doesn't like old add on.  It is rare that I have Firefox crash. 
It may get slow at times but it keeps chugging along.  Generally I have
four or five profiles running and sometimes even more.  I use different
profiles for different tasks with different add ons.  I've noticed that
the more add ons one has, the slower it tends to get.  I sort of spread
them out a bit. 

Dale

:-)  :-) 
gevisz
2018-09-16 11:40:02 UTC
Permalink
Post by Mick
Post by gevisz
Post by Mick
Something else I came across causing FF crashes here, was a bug with
profile- sync-daemon (recent thread of mine refers). I don't know if you
use psd, but I wasn't aware of this psd bug when you posted about your
problems. I only mention it now as another thing to check next time you
have FF crashing on you.
Thank you for additional information.
I have read in this mailing list (may be it was your thread) that using
profiles in firefox is another source of crashes. So, I do not use
profiles, and now hope that it means that I do not use psd as well. :)
Ah! No, they are too different things.
I have not read anywhere that the use of multiple user profiles causes FF to
crash. Perhaps some addons may do.
<<SNIP>>
I have nine Firefox profiles here. Any problems I have had have turned
out to be a bad add on. Sometimes I turn off auto update and new
Firefox doesn't like old add on.
Probably, you meant that problems with old add ons arise when firefox
auto update is turned on. If so, I do agree.
It is rare that I have Firefox crash.
Unfortunately, even a rare Firefox crash has long standing consequences. :(
It may get slow at times but it keeps chugging along. Generally I have
four or five profiles running and sometimes even more. I use different
profiles for different tasks with different add ons. I've noticed that
the more add ons one has, the slower it tends to get. I sort of spread
them out a bit.
If multiple Firefox profiles do not increase the probability of its crash
any more, than it is a good news because they are really useful.

Anyway, I still afraid to use them so far.
Mick
2018-09-16 11:50:01 UTC
Permalink
Post by gevisz
Post by Mick
Post by gevisz
Post by Mick
Something else I came across causing FF crashes here, was a bug with
profile- sync-daemon (recent thread of mine refers). I don't know if you
use psd, but I wasn't aware of this psd bug when you posted about your
problems. I only mention it now as another thing to check next time you
have FF crashing on you.
Thank you for additional information.
I have read in this mailing list (may be it was your thread) that using
profiles in firefox is another source of crashes. So, I do not use
profiles, and now hope that it means that I do not use psd as well. :)
Ah! No, they are too different things.
I have not read anywhere that the use of multiple user profiles causes
FF to crash. Perhaps some addons may do.
<<SNIP>>
I have nine Firefox profiles here. Any problems I have had have turned
out to be a bad add on. Sometimes I turn off auto update and new
Firefox doesn't like old add on.
Probably, you meant that problems with old add ons arise when firefox
auto update is turned on. If so, I do agree.
It is rare that I have Firefox crash.
Unfortunately, even a rare Firefox crash has long standing consequences. :(
It may get slow at times but it keeps chugging along. Generally I have
four or five profiles running and sometimes even more. I use different
profiles for different tasks with different add ons. I've noticed that
the more add ons one has, the slower it tends to get. I sort of spread
them out a bit.
If multiple Firefox profiles do not increase the probability of its crash
any more, than it is a good news because they are really useful.
Anyway, I still afraid to use them so far.
I also have more than one profiles, with different/no addons and
configurations and have not experienced any crashes on my PC.
--
Regards,
Mick
Dale
2018-09-16 12:00:01 UTC
Permalink
Post by gevisz
I have nine Firefox profiles here. Any problems I have had have turned
out to be a bad add on. Sometimes I turn off auto update and new
Firefox doesn't like old add on.
Probably, you meant that problems with old add ons arise when firefox
auto update is turned on. If so, I do agree.
Well, that is sometimes why I turn auto update off on some add ons. 
Sometimes, since I am on a older version of Firefox, newer add ons don't
work.  I might add, some older add ons won't work with newer Firefox at
all.  Firefox disables them and works just not with the add on.  Tab
utilities is one of them. 
Post by gevisz
It is rare that I have Firefox crash.
Unfortunately, even a rare Firefox crash has long standing consequences. :(
I use session manager on most profiles and even if it does crash, I can
go back right away.  I don't recall losing anything.  On some profiles,
I have dozens of tabs open, sometimes close to and even over 100. 
Post by gevisz
It may get slow at times but it keeps chugging along. Generally I have
four or five profiles running and sometimes even more. I use different
profiles for different tasks with different add ons. I've noticed that
the more add ons one has, the slower it tends to get. I sort of spread
them out a bit.
If multiple Firefox profiles do not increase the probability of its crash
any more, than it is a good news because they are really useful.
Anyway, I still afraid to use them so far.
I been using profiles for a few years with no issues.  My biggest cause
of problems is incompatibility of add ons when either Firefox or the add
on gets updated.  It may be worth checking into again.  Could be that
all the new coding fixed issues you had before.  One thing about it, you
can always remove the newer profiles and go back to the old way. 

Dale

:-)  :-) 

gevisz
2018-09-16 11:30:02 UTC
Permalink
Post by Mick
Post by gevisz
Post by Mick
Something else I came across causing FF crashes here, was a bug with
profile- sync-daemon (recent thread of mine refers). I don't know if you
use psd, but I wasn't aware of this psd bug when you posted about your
problems. I only mention it now as another thing to check next time you
have FF crashing on you.
Thank you for additional information.
I have read in this mailing list (may be it was your thread) that using
profiles in firefox is another source of crashes. So, I do not use
profiles, and now hope that it means that I do not use psd as well. :)
Ah! No, they are too different things.
I have not read anywhere that the use of multiple user profiles causes FF to
crash. Perhaps some addons may do.
Multiple profiles for the same user.
Post by Mick
The use of psd on the other hand is a useful package, minimising the writing
cycles of the browser's cache to disk. If your PC is running on SDD or hybrid
disks and has enough RAM, then a profile-sync-daemon (when it is not buggy)
should be a good thing.
Ok, thank you for the information. I still use only HDDs. So, I
probably do not need psd so far.
Loading...