Skip to content

[BUG] Claude Code crashes with 100%+ CPU usage on ARM (v2.1.27) #22141

Closed as duplicate

Description

@christso

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

I'm using Ubuntu Linux on ARM. Previously, the Claude Code CLI was using 50% CPU, but now it's using over 100%, and the OS kills the process. This happens even with a basic prompt like "hello" - it freezes with 100%+ CPU and then crashes. It was working fine in version 2.1.25, so I've downgraded to that version.

Image

What Should Happen?

Claude Code should not use so much CPU. The performance should be as good as 2.1.25.

Error Messages/Logs

Steps to Reproduce

  1. launch claude
  2. type "hello" in the message area.
  3. top command shows 100% cpu usage, then after a minute or so the OS kills the process.

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.25

Claude Code Version

2.1.25

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Non-interactive/CI environment

Additional Information

No response

Activity

  1. github-actions commented on Jan 31, 2026

    @github-actions

    Found 3 possible duplicate issues:

    1. [BUG] Claude Code v2.1.27 freezes with 100% CPU on Synology NAS (Linux 4.4 kernel) — v2.1.25 works fine #22097
    2. [BUG] Claude Code 2.1.27 freezes after first message - regression from 2.1.25 #22103
    3. [BUG] Regression in 2.1.27: Infinite CPU loop on project startup #22057

    This issue will be automatically closed as a duplicate in 3 days.

    • If your issue is a duplicate, please close it and 👍 the existing issue instead
    • To prevent auto-closure, add a comment or 👎 this comment

    🤖 Generated with Claude Code

  2. codemile commented on Jan 31, 2026

    @codemile

    workaround: #22103 (comment)

  3. github-actions commented on Feb 8, 2026

    @github-actions

    This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.

  4. locked as resolved and limited conversation to collaborators on Feb 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions