Activity log for bug #1437070

Date Who What changed Old value New value Message
2015-03-26 22:43:38 A. Eibach bug added bug
2015-03-26 22:43:38 A. Eibach attachment added gdb_chromium.txt https://bugs.launchpad.net/bugs/1437070/+attachment/4357436/+files/gdb_chromium.txt
2015-03-26 23:14:31 A. Eibach description My CPU does not support SSE2, this is a fact. And as far as I knew, there was nowhere a *requirement* listed that for the use of Chromium, a SSE2-capable CPU would be mandatory. For instance, old(er) Athlon XP machines support SSE, but not SSE2. I've run a DEBUG build of chromium v41 to demonstrate this fact. These are the most evident 2 lines: # # Fatal error in ../../v8/src/ia32/assembler-ia32.cc, line 82 # CHECK(cpu.has_sse2()) failed # Looks to me that the _asm routines _blindly_ assume that the CPU is capable of SSE2 instruction set. At least the browser should exit more gracefully if this is the case, but not crash with a SIGILL. My CPU does not support SSE2, this is a fact. And as far as I knew (unless I missed something) for the use of Chromium on Linux, there was nowhere a *requirement* listed that a SSE2-capable CPU would be mandatory. For instance, old(er) Athlon XP machines support SSE, but not SSE2. I've run a DEBUG build of chromium v41 to demonstrate this fact. These are the most evident 2 lines: # # Fatal error in ../../v8/src/ia32/assembler-ia32.cc, line 82 # CHECK(cpu.has_sse2()) failed # Looks to me that the more recent _asm routines now _blindly_ assume that the CPU is capable of SSE2 instruction set. If you really DO want to lock us out (I think we still are millions of users worldwide with Athlon XP machines), we can't stop you. But at least the browser should exit more gracefully if this is the case, but not crash with a SIGILL.
2015-03-26 23:14:57 A. Eibach description My CPU does not support SSE2, this is a fact. And as far as I knew (unless I missed something) for the use of Chromium on Linux, there was nowhere a *requirement* listed that a SSE2-capable CPU would be mandatory. For instance, old(er) Athlon XP machines support SSE, but not SSE2. I've run a DEBUG build of chromium v41 to demonstrate this fact. These are the most evident 2 lines: # # Fatal error in ../../v8/src/ia32/assembler-ia32.cc, line 82 # CHECK(cpu.has_sse2()) failed # Looks to me that the more recent _asm routines now _blindly_ assume that the CPU is capable of SSE2 instruction set. If you really DO want to lock us out (I think we still are millions of users worldwide with Athlon XP machines), we can't stop you. But at least the browser should exit more gracefully if this is the case, but not crash with a SIGILL. My CPU does not support SSE2, this is a fact. And as far as I knew (unless I missed something) for the use of Chromium on Linux, there was nowhere a *requirement* listed that a SSE2-capable CPU would be mandatory. For instance, old(er) Athlon XP machines support SSE, but not SSE2. I've run a DEBUG build of chromium v41 to demonstrate this fact. These are the most evident 2 lines: # # Fatal error in ../../v8/src/ia32/assembler-ia32.cc, line 82 # CHECK(cpu.has_sse2()) failed # Looks to me that the more recent _asm routines now _blindly_ assume that the CPU is capable of SSE2 instruction set. If you really CAN'T help the cool feeling of locking us out (I think we still are millions of users worldwide with Athlon XP machines), we can't stop you. But at least the browser should exit more gracefully if this is the case, but not crash with a SIGILL.
2015-03-27 00:44:00 Chad Miller chromium-browser (Ubuntu): assignee Chad Miller (cmiller)
2015-03-27 15:32:21 Chad Miller bug watch added http://code.google.com/p/chromium/issues/detail?id=348761
2015-03-27 15:32:21 Chad Miller bug task added chromium-browser
2015-03-27 16:02:46 Chad Miller chromium-browser (Ubuntu): status New Incomplete
2018-03-09 13:31:01 Olivier Tilloy chromium-browser (Ubuntu): assignee Chad Miller (cmiller)
2018-03-09 13:31:56 Olivier Tilloy chromium-browser (Ubuntu): status Incomplete Fix Released