Hello. It's my first bug report. the package google-chrome-unstable-92.0.4512.4 segfaults immediately. dmesg output: [167361.389581] chrome[956617]: segfault at 10014a ip 000055baff0744b5 sp 00007ffe9bad50a0 error 6 in chrome[55bafa897000+84ab000] [167361.389589] Code: 0f 47 f7 44 89 f7 e8 3a 00 00 00 48 89 df e8 32 01 00 00 8b 43 10 8b 4b 18 0f b6 c0 c1 e0 0c 0f b6 c9 c1 e1 14 09 c1 44 09 f1 <44> 88 39 45 88 3e bf 01 00 00 00 e8 ab 81 cc 03 cc cc cc cc cc cc [167361.393997] chrome[956618]: segfault at 10014a ip 000055baff0744b5 sp 00007ffe9bad50a0 error 6 in chrome[55bafa897000+84ab000] (and more of those lines) console output on second start and after that: [957351:957351:0526/061003.363964:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. [957351:957351:0526/061003.708140:ERROR:raster_decoder.cc(996)] ContextResult::kFatalFailure: chromium_raster_transport not present (last line repeats often) console output on first start: ...something about bpf error 0330. Cant restart right now. the previous version 92.0.4496.0 worked fine, but i cant go back because it's ebuild is deleted after emerge -sync. thanks.
Hi, thank you for the report! Just so you know it makes bugs a lot easier to assign if you put the full atom in the summary with a description of the problem, i.e. "www-client/google-chrome-unstable: segfault at startup"
I just bumped www-client/google-chrome-unstable to 92.0.4515.20. Might need some time to hit the mirrors. Can you re-check with it?
(In reply to Stephan Hartmann from comment #2) > I just bumped www-client/google-chrome-unstable to 92.0.4515.20. Might need > some time to hit the mirrors. Can you re-check with it? Hi. Version 92.0.4515.20 works again. BIG thanks! @john: next time i do.
