jMonkeyEngine / jMonkeyEngine/sdk
Memory Leak
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 348
- Forks
- 104
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
Sadly I don't have anything specific. I was using sdk as normal, coding, opening and closing some models and after a while (2 hours or so) my RAM usage was at 100%. I restarted the SDK and after it got back up and running memory usage was only about 50%.
I suspect that there is some memory leak in scene composer, since I did open and close several megabytes big j3o a lot of times.
Contributor guide
No contributing guide indexed for this repository
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
The report provides no file or test to start from. Begin by reproducing the issue in Scene Composer with repeated opening and closing of large .j3o models, while monitoring RAM usage over time. Done means the suspected leak is identified and repeated model open/close cycles no longer cause unbounded memory growth.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100