Stable memory leaks
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 7.8k
- Forks
- 1.2k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 49
Description
Release Type: Official Release
Version: 4.0.0.1-beta04-1254 (.NET Core 3.1.6)
Platform(s): Windows
Describe the bug
If you leave the engine on for a couple of hours, gradually it will start to take up more and more memory, until the moment it runs out.
To Reproduce
Steps to reproduce the behavior:
- Just leave the engine on for a couple of hours
Expected behavior
That the engine won't take up all of my RAM
Screenshots
Log and callstacks
Stride process dump, during the leak https://mega.nz/file/uBlmiarD#R6NUiKj1EdTR7-_dEeYP1sc2XcXzMIR-jfUvPo2xXTM
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 leak on Windows using the issue's steps: leave the engine running for several hours while monitoring memory. Inspect the linked Stride process dump from during the leak to identify where growth occurs. Done means the cause is isolated, memory use remains stable during the same long-running test, and the fix is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100