PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding
vram leak
Open
Nobody has claimed this yet.
bug
- Dominant language
- Lua
- Stars
- 5.4k
- Forks
- 2.4k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 26
Description
Check version
- I'm running the latest version of Path of Building and I've verified this by checking the changelog
Check for duplicates
- I've checked for duplicate open and closed issues by using the search function of the issue tracker
What platform are you running Path of Building on?
Linux - Wine
How is Path of Building expected to behave?
nvtop output:
1gb VRAM
1.7gb RAM
Version: ~dev
Wine: i tried stock wine, proton, proton-experimental, same issues
How does Path of Building behave?
VRAM should remain low and stable
How to reproduce the issue
Open and close builds, over time it'll just grow, never shrink, suggesting GPU resources not properly disposed
PoB for PoE1 build code
Screenshots
No response
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
Reproduce the issue on Linux under Wine by opening and closing builds while monitoring VRAM and RAM with nvtop. Trace the build-opening and closing paths to identify where GPU resources remain allocated; done means VRAM remains low and stable over repeated cycles.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, lua
- Domain
- desktop, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100