# High CPU Utilization Issue

**URL:** <https://community.mappedin.com/t/high-cpu-utilization-issue/610>\
**Category:** Mappedin SDK for React Native\
**Tags:** android, ios, react-native\
**Created:** [October 14, 2026, 6:42am UTC](https://community.mappedin.com/t/high-cpu-utilization-issue/610 "2026-10-14T06:42:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Suresh\_S](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.mappedin.com/suresh_s/32/463_2.png) [@Suresh\_S](https://community.mappedin.com/u/Suresh_S)\
**Post date:** [October 14, 2026, 6:42am UTC](https://community.mappedin.com/t/high-cpu-utilization-issue/610/1 "2026-10-14T06:42:45Z")

</div>

Hi Mappedin Community,

We are experiencing significant CPU, memory, and responsiveness issues after mounting a Mappedin map once in our react native application (in both android and ios).

**Issues observed:**

- CPU randomly exceeds 100% during navigation, scrolling, and clicking, sometimes for 20–30 seconds.
- Map clicks can take over 30 seconds to load. During this time, other clicks and navigation are blocked.
- Memory remains high after 30 seconds of inactivity and after navigating back.
- Each additional map click appears to increase memory by approximately 100 MB.
- Only one map instance was mounted during this test.

**Before and after mounting the map:**

| Scenario | Metric | Before Map Mount | After Map Mount |
| --- | --- | --- | --- |
| A | Interaction CPU | 94% | 163% |
| A | Interaction memory | 697 MB | 1,331 MB |
| A | Memory after 30s idle | 680 MB | 1,229 MB |
| B | Interaction CPU | 73% | 146% |
| B | Interaction memory | 620 MB | 1,178 MB |
| B | Memory after 30s idle | 616 MB | 1,147 MB |
| C | Interaction CPU | 71% | 103% |
| C | Interaction memory | 624 MB | 1,147 MB |
| C | Memory after 30s idle | 623 MB | 1,096 MB |

Across 12 tested flows:

- Average interaction CPU increased from **68% before map mount** to **98% after map mount**.
- Average interaction memory increased from **476 MB before map mount** to **957 MB after map mount**.
- After mounting the map, 9 of 12 flows exceeded 100% CPU.

Are there any known issues or recommended lifecycle, cleanup, event-listener, rendering, or caching practices that could help?

Thank you.

---

<div class="post-metadata">

**Author:** ![msohm](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.mappedin.com/msohm/32/6_2.png) [@msohm](https://community.mappedin.com/u/msohm)\
**Post date:** [October 19, 2026, 3:18pm UTC](https://community.mappedin.com/t/high-cpu-utilization-issue/610/2 "2026-10-19T15:18:43Z")

</div>

I’m not aware of any known issues with the Mappedin SDK for React Native that would cause poor performance that you describe. We do have some tips on optimization here: [Getting Started | Mappedin](https://developer.mappedin.com/react-native-sdk/getting-started#optimizing-user-interface-performance)

1. What version are you using?
2. Do you see this behaviour with the example app? [react-native/SDKv6\_Examples/PlaygroundSamples at master · MappedIn/react-native · GitHub](https://github.com/MappedIn/react-native/tree/master/SDKv6_Examples/PlaygroundSamples)
3. Are you able to provide a basic project that reproduces this behaviour?
4. What device(s) and Android versions are you seeing this on?