🐞 [Bug]:

[RagweedChef]

Before submitting

• I have searched existing issues to make sure this bug hasn't already been reported
• I have updated to the latest version of the software to verify the issue still exists

Firmware Version

2.7.15

What did you do?

The latest version of the app , downloadable on June 28, starts off by running smoothly as it should, but within 6 to 10 minutes and views menu pages , using the map, scrolling in and out, the app begins to move very choppy and maps are very slow to render, this is repeatable, and it can only be corrected by completely closing the app and restarting it to where it runs smooth again and after 6 to 10 minutes is running at a snails pace and is unusable.

Expected Behavior

For the app to continue to run smoothly and be usable.

Current Behavior

App in iOS (latest version on June 28,2026) after 6 min the app becomes unusable. The map rendering becomes extremely slow and choppy, when you press the different buttons along the bottom of the app to change between the node screen, the settings screen, the connection screen, and the map screen those menus are choppy and do not flow well. The only way to make the app run smoothly as it should is to swipe it up and close it and reopen it.. It will work again for about the same amount of time before it slows down. This happens every single time.

Participation

• I am willing to submit a pull request for this issue.

Additional comments

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

🤖 Bug Report Received

Thank you for this detailed bug report! A maintainer will review it and investigate the root cause.

If you can provide any of the following it will speed up the investigation:

• Device logs from the Debug Log feature
• Whether this is a regression (last known-good firmware version)
• A minimal set of steps that consistently reproduce the issue

[github-actions]

🤖 Bug Report Received

Thank you for this detailed bug report! A maintainer will review it and investigate the root cause.

If you can provide any of the following it will speed up the investigation:

• Device logs from the Debug Log feature
• Whether this is a regression (last known-good firmware version)
• A minimal set of steps that consistently reproduce the issue

[bruschill]

I ran some perf tests comparing the current map against the upcoming map rewrite (#1989) — looks like that change fixes this.

Identical 5-min test on a 400-node mesh:

Resting CPU (app idle)	current	with rewrite (#1989)
Right after load	~31%	~31%
After 5 min of panning	~102%	~36%

Should be resolved whenever the map work ships 👍🏻

[garthvh]

Fixed by #1989 — the Map tab was rewritten from the SwiftUI Map to an MKMapView-backed implementation (ClusterMapView + MeshMapMK), which resolves the choppiness/degradation-under-use you hit on 2.7.15. Profiling on a 400-node mesh showed resting CPU after 5 min of panning drop from ~102% (old map) to ~36% (rewrite). This ships in 2.7.16, with additional ingestion/perf work (#2106) on top. Please reopen if you still see the slowdown on 2.7.16 or later.