iOS 26 Simulator - Extreme Memory Usage on M1 Pro

Question

Created 1w

Replies 3

Boosts 0

Participants 2

Hi everyone, Is anyone else seeing massive memory usage with the iOS 26 simulator? On my M1 Pro MacBook Pro (16GB RAM) running macOS 26, the simulator consumes all available memory, making my Mac extremely slow. This seems to be a memory leak. For comparison, the iOS 18.5 simulator runs perfectly fine and uses very little RAM. I've already tried restarting, but the issue persists. Has anyone found a workaround for this? Thanks.

Answered by DTS Engineer in 842726022

Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports.

Bug Reporting: How and Why? has tips on creating your bug report.

Boost

Answer 1

DTS Engineer OP

Apple

1w

Recommended

Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports.

Bug Reporting: How and Why? has tips on creating your bug report.

1

Answer 2

ppucc OP

1w

Probably the problem is in xcode. I tried to switch to the latest stable version and go back to the beta one. Now it works however my ram usage is really high

0

Answer 3

DTS Engineer OP

Apple

4d

Maybe a little legwork to try and isolate the problem might be worthwhile. Are the memory problems limited to one project or can you reproduce them using a new template project in Xcode? If you can't reproduce them with a template then maybe instrumenting the memory usage in your app.

If neither of those things help, then maybe it's something to do with files cached on your machine. To check and see if it has anything to do with files cached in the local user directory on your machine you might consider creating a new local user and building the app while logged as that user. That'll isolate any cached files stored in your other user directory.

0