2. Disable all addons as you log in aside from this one. (For a less rigorous test you can enable an addon to track memory usage too.)
3. Note the memory usage of the single addon. (From mouseover of Game Menu microbutton if you don't have an memory usage addon enabled.)
4. Open the world map and put the mouse over it.
5. Periodically check memory usage.
On my client, the 3k attributed to the addon balloons to 3 MB within a minute. It will reset periodically (meaning it's likely garbage being collected) and then march back up.
With multiple addons having a data provider, one unlucky addon gets the blame and I've seen it add 5MB within a minute before dropping back.
Has anyone else noticed this behavior? Is there something we can do to minimize it? Or is it accepted behavior and we should ignore it?
This happens with my addon, but the cursor need not be on the world map. I have the cursor over the game menu and I see the addon memory usage climb and then when garbage collection kicks in, go back down.
The more pins on the map, the quicker the memory usage rises. None of my map data code is being called as this is happening. Therefore I believe the issue is with Blizzard's code.
This is a similar issue but not the same. I had noticed this before when I was doing some stuff with HereBeDragons and I contacted the author because I thought it was a bug with HBD but they tracked it down to the maps label provider. When you have your mouse over the map it is running an update function that contains C_Map.GetMapInfoAtPosition. That memory usage is then blamed on the first addon loaded that has any map data provider code.