On 13/08/2020 19:53, peter green wrote:
thank you for packaging chromium.
after upgrading libc to 2.31, all available chromium: 80 and 83 are cashing.
the bug has been treated at redhat:
https://bugzilla.redhat.com/show_bug.cgi?id=1773289
and has been confirmed by upstream:
https://bugs.chromium.org/p/chromium/issues/detail?id=1025739
hope my report will help,
alex
I can confirm that chromium is crashing in Sid on i386 (and also raspbian
bullseye)
, but the bugs you link to have already been fixed.
I think the current crash is a similar issue but with a different syscall,
namely
clock_gettime64. I will try to whip up a patch.
Ok, I added clock_gettime64 to the whitelist and tested the browser in a debian
sid
i386 vm and on a raspbian bullseye system. On the former the browser seemed to
work
ok (at least it can load duckduckgo google and slashdot without crashing) but
on the
latter it ran into errors with two additional syscalls. 0407
__NR_clock_nanosleep_time64
and 0412 __NR_utimensat_time64
I'm not sure if this was adifference between the architectures (though I can't
think
why it would be), a timing difference, a difference in graphics stacks, or a
configuration
difference (the raspbian bullseye system still has configuration left by the
raspberry
pi image the system started from including an installation of ublock origin)
but I think
it makes sense to put them on the whitelist too (their 32-bit time counterparts
are
on the whitelist).
I have added them to the whitelist and am currently doing test builds.
