Freezing with high CPU usage on Apple Silicon (M1/M2)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 12.9k
- Forks
- 2k
- Avg merge
- 4h 27m
- Merged PRs (30d)
- 8
Description
Since a long time many different people are reporting issues running Tiled on their M1 / M2 Macs, most frequently on [this forum thread](https://discourse.mapeditor.org/t/it-cant-work-well-on-apple-m1-pro-monterey/5814).
I hoped a Universal build that included native ARM64 support would help with the issue, but that shipped with [Tiled 1.10.2](https://github.com/mapeditor/tiled/releases/tag/v1.10.2) and the problem is still being reported.
**Describe the bug**
Various quotes from the above forum thread:
> I installed Tiled 1.10, 1.9 and 1.8 and all versions have the same problem. Tiled is randomly stuck loading. I use an older Macbook Pro 2015 but with Monterey installed.
> The latest version freezes randomly. High CPU usage.
> I’m using mac (M1 chip) ,OS Sonoma 14.2.1, I tried using older versions of Tiled as well. Current issue is that I get the spinning wheel of death, this happens after a minute of using the App. This causes the app to freeze and I have to close it out and restart it. It always crashes after the same amount of time.
**To Reproduce**
So far this problem has only been reported on M1 / M2 hardware, which is likely necessary to reproduce the problem. I don't have access to such hardware myself.
Tiled Version: Reportedly happened also with 1.7.2 (possibly earlier) and up to 1.10.2
**How to Help**
If you can reproduce this issue on your macOS system, please try to set up a Qt development environment by installing Qt and Xcode, then see if you can also reproduce the issue with your own build of Tiled. If it happens, it could help to run Tiled in the debugger and pause it, to see where it is getting stuck.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is named. Set up Qt and Xcode, build Tiled yourself on an affected M1/M2 macOS system, reproduce the freeze, and pause it in the debugger to identify where it is stuck. Done means locating the cause of the high CPU freeze and confirming the fix on the affected hardware.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, macos
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100