https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68853
--- Comment #9 from Markus Trippelsdorf <trippels at gcc dot gnu.org> --- Thanks Andrew. Turned out the issue from comment 2 is similar. Both issues are solved with -fno-delete-null-pointer-checks. Maybe the chromium devs should add that flag to their default gcc flags...
