** Description changed: 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. + 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 _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. + 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.
** Description changed: 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. + 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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1437070 Title: chromium-browser crashes with SIGILL if CPU does not support SSE2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1437070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
