Unexpected large memory usage when using large images
Open
Nobody has claimed this yet.
bug
- Dominant language
- C#
- Stars
- 7.8k
- Forks
- 1.2k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 49
Description
Release Type: Official Release
Version: 4.1.0.1457
Platform(s): Windows
Describe the bug
When adding large images (for example 3000x9000) stride memory usage spikes suddenly.
To Reproduce
Steps to reproduce the behavior:
- Create empty project and add a sprite sheet asset.
- Add a sprite and select a large image (can be easily created using paint for example).
Expected behavior
Memory usage shouldn't be this large, images with mentioned size can spike memory usage even by 1GB (Worst I got is 7GB total).
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 issue in an empty Stride project on Windows with a sprite sheet asset and a large image such as 3000x9000, then profile memory while selecting the sprite. Done means the large image no longer causes an excessive memory spike, such as the reported 1–7 GB increase.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- game-dev, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100