Chromium complains about stack smashing whenever started. I'm starting it from
an xterm, and the output when starting to a blank tab with Google as the search
engine is:

[122740:122740:0126/025300.330856:ERROR:gpu_init.cc(457)] Passthrough is not supported, GL is disabled, ANGLE is
[122696:122727:0126/025301.818616:ERROR:nss_util.cc(286)] After loading Root Certs, loaded==false: NSS error code: -8018
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[122696:122727:0126/025304.329684:ERROR:chrome_browser_main_extra_parts_metrics.cc(227)] START: ReportBluetoothAvailability(). If you don't see the END: message, this is crbug.com/1216328.
[122696:122727:0126/025304.329873:ERROR:chrome_browser_main_extra_parts_metrics.cc(230)] END: ReportBluetoothAvailability()
*** stack smashing detected ***: terminated

With Google as the default search engine, opening a new tab will give me two
more "*** stack smashing detected ***: terminated" lines.

(Note: I disabled hardware acceleration to see if it would make the stack
smashing go away, it didn't.)

If I set the default search engine to Debian, I get:

[122448:122448:0126/025217.558330:ERROR:gpu_init.cc(457)] Passthrough is not supported, GL is disabled, ANGLE is
[122405:122461:0126/025219.779173:ERROR:nss_util.cc(286)] After loading Root Certs, loaded==false: NSS error code: -8018
[122405:122432:0126/025221.869024:ERROR:chrome_browser_main_extra_parts_metrics.cc(227)] START: ReportBluetoothAvailability(). If you don't see the END: message, this is crbug.com/1216328.
[122405:122432:0126/025221.869057:ERROR:chrome_browser_main_extra_parts_metrics.cc(230)] END: ReportBluetoothAvailability()
*** stack smashing detected ***: terminated

The stack smashing messages go away when I upgrade to 97.0.4692.99-1 (in
    unstable).


I don't see stack smashing messages running Chromium 100.0.4853.0 (Build
revision 963308, linux binary downloaded from chromium.org's recommended
source).
I also don't see stack smashing messages if I switch to unstable and upgrade
Chromium to 97.0.4692.99-1 (which pulls in an updated libc, among other
things. I'll include the system info for the unstable version in this message
too)

Ordinarily I wouldn't bother reporting a bug that appears fixed in unstable,
but the stack smashing messages seem like they may be a sign of a security
hole - and the fact that they appear linked to third-party network service
integration makes them seem a bit ominous.

On Wed, 26 Jan 2022 03:50:53 +0200 Spiky Caterpillar wrote:
 >
 > Chromium complains about stack smashing whenever started. I'm
starting it from
 > an xterm, and the output when starting to a blank tab with Google as
the search
 > engine is:
 >
 > [122740:122740:0126/025300.330856:ERROR:gpu_init.cc(457)] Passthrough
is not supported, GL is disabled, ANGLE is
 > [122696:122727:0126/025301.818616:ERROR:nss_util.cc(286)] After
loading Root Certs, loaded==false: NSS error code: -8018
 > *** stack smashing detected ***: terminated
 > *** stack smashing detected ***: terminated
 >
[122696:122727:0126/025304.329684:ERROR:chrome_browser_main_extra_parts_metrics.cc(227)]
START: ReportBluetoothAvailability(). If you don't see the END: message,
this is crbug.com/1216328.
 >
[122696:122727:0126/025304.329873:ERROR:chrome_browser_main_extra_parts_metrics.cc(230)]
END: ReportBluetoothAvailability()
 > *** stack smashing detected ***: terminated


The stack smashing errors are related to building with the clang-11
compiler; the reason you don't see them with unstable's version of
chromium is because unstable uses clang-13. Similarly, upstream google's
chromium builds against some clang-14 pre-release. I could disable stack
protection from the stable builds of chromium, but stack protection
could potentially be useful for actual security bugs. So for now, I'm
planning to just leave it enabled and ignore the messages.

At some point, it is likely that clang-13 will be backported to stable
(similar to how clang-11 was backported to oldstable, which allowed
firefox-esr to use it instead of oldstable's clang-7). Once that
happens, I plan to use clang-13 for building chromium in stable, and the
messages will go away.


 > [122448:122448:0126/025217.558330:ERROR:gpu_init.cc(457)] Passthrough
is not supported, GL is disabled, ANGLE is
 > [122405:122461:0126/025219.779173:ERROR:nss_util.cc(286)] After
loading Root Certs, loaded==false: NSS error code: -8018
 >
[122405:122432:0126/025221.869024:ERROR:chrome_browser_main_extra_parts_metrics.cc(227)]
START: ReportBluetoothAvailability(). If you don't see the END: message,
this is crbug.com/1216328.
 >
[122405:122432:0126/025221.869057:ERROR:chrome_browser_main_extra_parts_metrics.cc(230)]
END: ReportBluetoothAvailability()
 > *** stack smashing detected ***: terminated
 >
[...]

 > hole - and the fact that they appear linked to third-party network
service
 > integration makes them seem a bit ominous.


The nss_util.cc error is unrelated to the stack smashing errors, and
it's also one that I haven't seen before. It's pretty odd; it's from
LoadNSSModule("Root Certs", "libnssckbi.so", nullptr) failing to load
that library. I see that you have libnss3 (from stable) installed, so
I'm wondering what's going on. That error is coming from libnspr4
(PR_GetError), and I couldn't find it in the source code but I did find
it on a mozilla developer webpage as SEC_ERROR_UNKNOWN_PKCS11_ERROR. It
seems to say that it's failing to load a certificate, so maybe there's
something wrong your root certificates? I'm not entirely sure where it's
finding the root certificates, they might be built into the nss3 library
or they might be in /etc/ssl/certs/.

Do you have the ca-certificates package installed? Does https work
normally in the browser?

On Wed, 26 Jan 2022 03:11:16 -0500 Andres Salomon wrote:
 > > *** stack smashing detected ***: terminated
 > >


I backported clang-13 to debian stable and used it to build chromium.
Nothing else was backported or changed (other than the requisite changes
needed to tell chromium to use clang-13 and friends instead of clang).
The stack smashing error messages disappeared. So this is absolutely an
issue with building against clang-11 in stable.

Dear Maintainer,

I recently installed debian 12 32-bit and then installed chromium. The build
version was 130.0.6723.116. Later, chromium was automatically updated with the
new build 131.0.6778.85. The stack smashing error has now reappeared (end
output below)

*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[32254:32254:1129/112914.857767:ERROR:gpu_process_host.cc(982)] GPU process
exited unexpectedly: exit_code=6
[32254:32254:1129/112914.857842:FATAL:gpu_data_manager_impl_private.cc(423)]
GPU process isn't usable. Goodbye.
[1129/112914.979022:ERROR:elf_dynamic_array_reader.h(64)] tag not found
Trace/breakpoint trap

Perhaps the build for the 32-bit version had reverted to clang-11. Would
appreciate a new working build. Thanks.