2072 / 2072/Decursive

Memory Leak

Open
#20 7 comments 0 reactions 1 assignee Claimed by @2072 View on GitHub
Blizzard issue bug
Dominant language
Lua
Stars
11
Forks
16
Avg merge
2d 6h
Merged PRs (30d)
1

Description

I have been troubleshooting another issue when I noticed that Decursive about every 20-30 seconds grows to about 200+ MB of memory usage before Garbage Collection kicks in and it drops back down off the list. And than I watch it grow back up to 200+ MB again over and over. Obviously GC takes care of the leaked memory, but it's not free, and might be something worth looking at. I've honestly never noticed it before, but I also don't watch my addon memory usage that often either. So not sure how long it's been doing this.

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue describes a periodic memory growth in a World of Warcraft addon. Start by profiling the addon's memory usage in-game or with a WoW addon debugger. Look for loops, event handlers, or data structures that accumulate objects without release. The goal is to identify the source of the allocation and ensure proper cleanup.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.