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.