FS#19647 - chromium 5.0.396.0 segfaulting when built with gcc 4.5

Attached to Project: Arch Linux
Opened by Tom Killian (tomk) - Sunday, 30 May 2010, 12:25 GMT
Last edited by Pierre Schmitz (Pierre) - Monday, 07 June 2010, 09:50 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Dan Griffiths (Ghost1227)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 9
Private No

Details

Description: chromium 5.0.396.0 segfaults, does not display any page


Additional info:
package version 5.0.396.0-1
kernel.log error message: kernel: chromium[6670]: segfault at 1 ip 00007fafd6633ab0 sp 00007fff28db2218 error 4 in libc-2.12.so[7fafd65b4000+153000]

Steps to reproduce:
Install chromium 5.0.396.0
run chromium
This task depends upon

Closed by  Pierre Schmitz (Pierre)
Monday, 07 June 2010, 09:50 GMT
Reason for closing:  Fixed
Additional comments about closing:  latest gcc fixed the problem
Comment by Tom Killian (tomk) - Sunday, 30 May 2010, 12:33 GMT
Additional error message when run from cli:
[5:5:68347361009:FATAL:base/process_util_linux.cc(504)] Check failed: false. Out of memory.
Comment by Pierre Schmitz (Pierre) - Sunday, 30 May 2010, 13:20 GMT
Afaik chromium cannot be build with gcc 4.5. Btw: Is there a reason to not use the stable version 5.0.375.55?
Comment by Tomas Mudrunka (harvie) - Sunday, 30 May 2010, 15:28 GMT
1.) should be reported upstream to gcc
2.) 5.0.375.55 have also problems with gcc 4.5: http://code.google.com/p/chromium/issues/detail?id=41887
- it can be avoided using: -O3 -fno-ipa-cp
- or there's a patch for svn version: http://aur.archlinux.org/packages/chromium-browser-svn/chromium-browser-svn/search-workaround.patch
Comment by Pierre Schmitz (Pierre) - Sunday, 30 May 2010, 15:40 GMT
I am currently building a version without ipa-cp. Let's see if that works. The 375.5 is the stable and maintained branch so it's recommend to sue that.
Comment by Pierre Schmitz (Pierre) - Sunday, 30 May 2010, 17:04 GMT
I tried using -fno-ipa-cp. I also tried that other workaround mentioned in the upstream bug report. Chromium still segfaults. I guess we need to wait for a fixed gcc.
Comment by Dan Griffiths (Ghost1227) - Sunday, 30 May 2010, 17:30 GMT
We are researching options. I was unaware that a stable branch had finally been released, so the arch package will be sticking with that for now. Otherwise, it does appear that gcc is at fault for the issues 64 bit users are experiencing.
Comment by Pierre Schmitz (Pierre) - Sunday, 30 May 2010, 17:48 GMT
I am trying to build it using gcc 4.4.
Comment by Tom Killian (tomk) - Sunday, 30 May 2010, 22:18 GMT
5.0.375.55 works - thanks.
Comment by Allan McRae (Allan) - Monday, 31 May 2010, 01:34 GMT
Has anyone filed a bug report to gcc bugzilla? I can not find one linked in any relevant bug reports.

And was this patch tried: http://aur.archlinux.org/packages/chromium-browser-svn/chromium-browser-svn/search-workaround.patch
According to the upstream bug report, the replace line is equavalent to the insert one but does not get miscompiled.
Comment by Pierre Schmitz (Pierre) - Monday, 31 May 2010, 04:44 GMT
That patch is only a workaround for the search bar when build with gcc 4.5. This is only valid for i686; on x86_64 gcc produces a binary which just segfaults on glibc on stratup. So on x86_64 this workaround does not help.
Comment by Allan McRae (Allan) - Monday, 31 May 2010, 05:01 GMT
So what are the proper upstream bug reports for this issue so I can track the fix for gcc? The only one linked here is for the search bar breakage.
Comment by Mikhail Vorozhtsov (mvorozhtsov) - Saturday, 05 June 2010, 08:32 GMT
gcc-4.5.0-4 seems to have fixed it (segfaults). Tested 5.0.375.70 and 6.0.422.0 on x86_64. 5.0.396.0 should be fine too.
Comment by Tomas Mudrunka (harvie) - Saturday, 05 June 2010, 11:45 GMT
wait what? i thought that -4 is only package release number which means no changes of upstream gcc source... how it can change quality of gcc produced binary?
Comment by Pierre Schmitz (Pierre) - Saturday, 05 June 2010, 11:53 GMT
A patch was added to fix khtml. There is a chance that this same patch also fixed chromium's webkit which was forked from khtml.

Loading...