meliorence / meliorence/react-native-snap-carousel
Autoplay memory usage
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 10.5k
- Forks
- 2.3k
- PR merge metrics
- No merged PRs in 30d
Description
Is this a bug report, a feature request, or a question?
This is a question.
When I am using autoplay={true}, the memory usage keeps growing and it is making jumps.

When I am using autoplay={false}, the memory usage is stable (above second part) but every time I slide an item, the memory increases as following. I am using PureComponent for each slide. Anyone face this problem before? When I left the app opened for a few hours, it gets to 1 - 2GB memory usage.

Have you followed the required steps before opening a bug report?
(Check the step you've followed - put an x character between the square brackets ([]).)
- [] I have read the guidelines regarding bug report.
- I have reviewed the documentation in its entirety, including the dedicated documentations 📚.
- I have searched for existing issues and made sure that the problem hasn't already been reported.
- I am using the latest plugin version.
- [] I am following the issue template closely in order to produce a useful bug report.
Have you made sure that it wasn't a React Native bug?
Yes.
Environment
Environment:
React: 16.9.0
React native: 0.61.4
react-native-snap-carousel: 3.8.4
Target Platform:
iOS Simulator (13.2.2)
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
Start by reproducing the reported memory growth with react-native-snap-carousel 3.8.4 on the stated React Native and iOS Simulator versions, comparing autoplay={true} and autoplay={false}. Use the memory profiler while sliding items and determine whether the issue is in the carousel or the slide components; done means identifying a reproducible cause and documenting a verified resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react, react-native
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100