Bug 2381542 - Chromium 138 Illegal Instruction
Summary: Chromium 138 Illegal Instruction
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: chromium
Version: 41
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-07-16 21:58 UTC by Bernie Hoefer
Modified: 2025-07-18 16:30 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Bernie Hoefer 2025-07-16 21:58:23 UTC
I'm running Fedora Linux 41 on an Intel(R) Pentium(R) CPU G2030 @ 3.00GHz machine.  Its window manager is (non-Wayland) Xfce.

After updating from:
  chromium-137.0.7151.103-1.fc41.x86_86
to:
  chromium-138.0.7204.49-1.fc41.x86_86
...it will no longer start. Trying to start it from the command line:


  $ chromium-browser about:blank
  Illegal instruction (core dumped)


...but no vmcore is left in my $HOME or /tmp. Updating to chromium-138.0.7204.100-1.fc41.x86_86 did not resolve the issue.

I've read that "Illegal instruction" means that a CPU instruction was executed that is not valid for my CPU.  I've looked through Chrome's release notes but nothing stands out as a possible cause.

As a final data point, I'm also running Fedora Linux 41 on a AMD Ryzen 7 PRO 8840HS w/ Radeon 780M Graphics (again with non-Wayland Xfce) and Chromium works fine there. So again I'm wondering if there is something about my old Intel CPU causing Chromium to crash.

Reproducible: Always

Comment 3 Mr. Beedell, Roke Julian Lockhart (RJLB) 2025-07-17 16:00:04 UTC
Is https://discussion.fedoraproject.org/t/where-is-chromiums-debuginfo-package/159053 an example of this?

Comment 4 Bernie Hoefer 2025-07-17 16:16:40 UTC
(In reply to Mr. Beedell, Roke Julian Lockhart (RJLB) from comment #3)
===
> Is
> https://discussion.fedoraproject.org/t/where-is-chromiums-debuginfo-package/
> 159053 an example of this?
===

I do not think so.  My strace output (which has been attached to this Bugzilla ticket as a private attachment) shows:

  --- SIGILL {si_signo=SIGILL, si_code=ILL_ILLOPN, si_addr=0x7fa01939439d} ---
  +++ killed by SIGILL (core dumped) +++

...and it and my abrt output does not mention anything about the need for debug packages or symbols.


Note You need to log in before you can comment on or make changes to this bug.