Comment #36 on issue 9007 by a...@chromium.org: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
You can remove the SSE2 specific flags from the build and you'll still end
up with a
working browser. However, you can't run pixel-tests with such a browser
because your
Comment #35 on issue 9007 by brazentone: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
It seems chromium is built from the core to depend on SSE2. There does not
appear to
be a non-SSE2 branch, so I suppose anyone with an old Athlon or Coppermine
P3 will
have to
Comment #34 on issue 9007 by f...@sofaraway.org: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
src/build/common.gypi:
'conditions': [
[ 'OS=="linux"', {
'target_defaults': {
'asflags': [
# Needed so that libs with .s files (e.g. li
Comment #33 on issue 9007 by f...@sofaraway.org: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
I don't pass *any* flag that could be causing that.
My downstream builds rely on the rules provided by upstream (scons files,
now gyp).
I don't see how it could be my fau
Comment #32 on issue 9007 by Sandshrew: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
STOP posting outputs of cat /proc/cpuinfo and stack traces - as brazentone
already
CLEARLY stated above it's NOT a bug in chromium, but in the PACKAGES for
ubuntu
provided by FA
Comment #31 on issue 9007 by shao1555: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
I have a same problem. crash chromium on first run. - Xubuntu 8.10 (x86)
s...@nue % chromium-browser
[~]
[16540:16540:677054224:ERROR:/build/buil
Comment #30 on issue 9007 by m...@shoutdigital.co.uk: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
[7472:7472:2422980229:ERROR:common/temp_scaffolding_stubs.cc(194)] Not
implemented
reached in static bool FirstRun::IsChromeFirstRun()
Illegal instruction
boardm...@
Comment #29 on issue 9007 by Sandshrew: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
Now maybe someone can open a bug report here ->
https://bugs.edge.launchpad.net/~chromium-daily (can't figure out how to do
it
myself...) ?
--
You received this message because y
Comment #28 on issue 9007 by lewiscollard: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
Crap.
I hadn't even considered that Chromium might contain SSE2-specific assembly
code, and
that it was indeed an architectural choice rather than a Ubuntu build bug.
Appare
Comment #27 on issue 9007 by truthseekernz: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
Clearly requiring SSE2 was an architectural choice. I suppose the problem
is that it
leaves anyone running an AMD Athlon CPU in the position of not being able
to run
Chromiu
Comment #26 on issue 9007 by lewiscollard: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
shellster: issue "x/i $pc" in gdb after running to see which instruction is
causing
it to die. Your /proc/cpuinfo would come in handy, too.
We're still harassing the wrong peo
Comment #25 on issue 9007 by brazentone: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
We've now firmly asserted that the problem is the use of SSE2 instuctions
on non-SSE2
processors. Therefore it is not a Chromium bug but a packaging bug. Unless
they
uncover so
Comment #24 on issue 9007 by shellsterdude: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
I hope this helps. I just downloaded the latest copy of chromium, and the
problem
still exists. I have attached both gdb run of chromium and an strace
(seems to be
pretty
Comment #23 on issue 9007 by truthseekernz: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
Ok, here is the gdb output I got:
st...@kauri:~$ gdb chromium-browser
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or
Comment #22 on issue 9007 by 05china: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
the cpu must be support SSE2,
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your
Comment #21 on issue 9007 by flomar34: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
Maybe, this is the good question here
https://answers.launchpad.net/chromium-browser/+question/66086
--
You received this message because you are listed in the owner
or CC fields
Comment #20 on issue 9007 by lewiscollard: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
Bam. cvtsi2sd is an SSE2 instruction, which your processor does not support.
Looks like we're in the wrong place. :)
--
You received this message because you are listed in the
Comment #19 on issue 9007 by panther.ru: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
lewiscollard,
[12485:12485:11553322928:ERROR:common/temp_scaffolding_stubs.cc(194)] Not
implemented
reached in static bool FirstRun::IsChromeFirstRun()
[New Thread 0xb67e2b90 (L
Comment #18 on issue 9007 by lewiscollard: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
panther/truthseekernz: would you care to run gdb as per my earlier comment
so that we
can definitively nail this down as a Ubuntu build bug, rather than a
Chromium one?
--
Y
Comment #17 on issue 9007 by truthseekernz: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
Same problem here. Ubuntu 8.10 32-bit desktop.
st...@kauri:~$ chromium-browser
[27987:27987:523793513185:ERROR:common/temp_scaffolding_stubs.cc(194)] Not
implemented reached in
Comment #16 on issue 9007 by panther.ru: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
Ubuntu Intrepid.
$ chromium-browser
[11761:11761:10118677618:ERROR:common/temp_scaffolding_stubs.cc(194)] Not
implemented
reached in static bool FirstRun::IsChromeFirstRun()
Ill
Comment #15 on issue 9007 by lewiscollard: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
Here we go. Apologies to anyone that is notified of these follow-ups
receiving one so
soon after my last one.
y...@plz:~$ gdb chromium-browser
(gdb) run
Program received sig
Comment #14 on issue 9007 by lewiscollard: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
I'm getting the same issue on Ubuntu Hardy with the PPA builds, but it's
happen
somewhat differently to alex.evans above (although, interestingly, while
it's doing I/O):
y..
Comment #13 on issue 9007 by alex.evans: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
Is also occurring on my Athlon XP 1700. Running daily builds from Ubuntu
PPA. Going
to try building from svn rather than use the package which may be compiled
for a more
modern
Comment #12 on issue 9007 by twigmon: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
Still an issue with 2.0.172.0~svn20090326r12573-0ubuntu1~ucd1~intrepid
$ chromium-browser
[30085:30085:339051905494:ERROR:common/temp_scaffolding_stubs.cc(214)] Not
implemented reach
Comment #11 on issue 9007 by trampster: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
Just to clarify the NotImplemented is not the problem. people who have this
working
are still geting the NotImplemented in their terminal. The problem here is
the
"Illegal instr
Comment #10 on issue 9007 by coolaj86: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
I'm new to C and C++, but I've had this NotImplemented error in my own
projects.
It was a problem in the Makefile such that a certain object file wasn't
being
compiled, or it ha
Comment #9 on issue 9007 by brazentone: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
Not a problem with AMD arch, as the issue also happens on intel Coppermine
(P3's). So
it's either a trait common to two very different processors, or there's
another
commonality
Comment #8 on issue 9007 by shellsterdude: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
Same issue latest build and all previous builds. Possibly an issue with
the AMD
architecture?
cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family
Comment #7 on issue 9007 by twigmon: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
Problem still exists with 2.0.171.0~svn20090321r12248-0ubuntu1~ucd1~intrepid
$ chromium-browser
[7457:7457:178804741714:ERROR:common/temp_scaffolding_stubs.cc(214)] Not
implemented
Comment #6 on issue 9007 by brazentone: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
New svn build, problem remains.
2.0.171.0~svn20090320r12198-0ubuntu1~ucd1~intrepid
$ chromium-browser
[6991:6991:2458378967:ERROR:common/temp_scaffolding_stubs.cc(214)] Not
imp
Comment #5 on issue 9007 by gfsheppard: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
Same errors. Similar Processor.
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 10
model name : AMD Athlon(tm) XP 2800+
stepping
Comment #4 on issue 9007 by flomar34: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
Hi,
Same problem for me since the svn20090317r11882 and it was ok with the
svn20090311r11455
Xubuntu 8.10
--
You received this message because you are listed in the owner
or CC fiel
Comment #3 on issue 9007 by twigmon: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
I'm having the exact same problem here:
dan...@orange:/var/www/btf/frontend/btf$ cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model
Comment #2 on issue 9007 by brazentone: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
stats from the original bug:
Exact same cpuinfo and kernel build. I'm going to try with debugging
symbols compiled
in next.
--
You received this message because you are listed
Comment #1 on issue 9007 by frumious: Crash on First Run
http://code.google.com/p/chromium/issues/detail?id=9007
I get the same issue. My cpu info is below:
$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 8
model name : Pentium I
36 matches
Mail list logo
