Announcement

Collapse

Forum Rules

  • No flaming or derogatory remarks, directly or through insinuation.
  • No discussion, sharing or referencing illegal software such as hacks, keygen, cracks and pirated software.
  • No offensive contents, including but not limited to, racism, gore or pornography.
  • No excessive spam/meme, i.e. copious one liners in a short period of time, typing with all caps or posting meme responses (text/image).
  • No trolling, including but not limited to, flame incitation, user provocation or false information distribution.
  • No link spamming or signature advertisements for content not specific to Dota 2.
  • No Dota 2 key requests, sell, trade etc.
  • You may not create multiple accounts for any purpose, including ban evasion, unless expressly permitted by a moderator.

  • Please search before posting. One thread per issue. Do not create another thread if there is an existing one already.
  • Before posting anything, make sure you check out all sticky threads (e.g., this). Do not create new threads about closed ones.
  • It is extremely important that you post in correct forum section.

  • Balance discussion only in Misc.
  • All art related (such as hero model) feedbacks go to Art Feedback Forum.
  • All matchmaking feedback should go here: Matchmaking Feedback
  • All report/low priority issues should go here: Commend/Report/Ban Feedback
  • No specific workshop item feedback. These should go to workshop page of that item.
  • When posting in non-bugs section (such as this), use [Bugs], [Discussion] or [Suggestion] prefix in your thread name.



In case you object some action by a moderator, please contact him directly through PM and explain your concerns politely. If you are still unable to resolve the issue, contact an administrator. Do not drag these issues in public.



All rules are meant to augment common sense, please use them when not conflicted with aforementioned policies.
See more
See less

[Bug] Reported Memory leak issue with heavy use of GridNav:GetAllTreesAroundPoint

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • [Bug] Reported Memory leak issue with heavy use of GridNav:GetAllTreesAroundPoint

    In doing some performance testing I've run into an issue which appears to be GridNav:GetAllTreesAroundPoint leaking memory when called frequently. It's possible that it will be released at some point, but I have not seen that. If I run:

    Code:
    for i=1,30 do
      Timers:CreateTimer(function()
        GridNav:GetAllTreesAroundPoint(hero:GetAbsOrigin(), 5000, true)
        return .03
      end)
    end
    This code starts up 30 timers (thinkers) which each run once every frame (30 times a second, or .0333 seconds between runs), effectively calling GridNav:GetAllTreesAroundPoint() 900 times a second. In the particular test case there was around 600 trees found in the 5000 radius given. After several seconds of running, the console begins to spit out the following:

    Code:
    [ W VScript          ]: LUA Memory usage warning: The VM has hit a new high usage of 83,886,080 bytes.
    [ W VScript          ]: LUA Memory usage warning: The VM has hit a new high usage of 117,440,512 bytes.
    [ W VScript          ]: LUA Memory usage warning: The VM has hit a new high usage of 150,994,944 bytes.
    [ W VScript          ]: LUA Memory usage warning: The VM has hit a new high usage of 184,549,376 bytes.
    I cancelled all the running timers and waited several minutes, then started them again and quickly started receiving the following lines:

    Code:
    [ W VScript          ]: LUA Memory usage warning: The VM has hit a new high usage of 218,103,808 bytes.
    [ W VScript          ]: LUA Memory usage warning: The VM has hit a new high usage of 251,658,240 bytes.
    This leads me to believe that the entities returned by this function are remaining resident in memory in lua. I recognize that this is an absurdly excessive amount of calls to make (with such a large radius especially), but I felt it still potentially merits concern that the memory is potentially not getting cleaned up correctly.

    Thanks for your consideration of this issue,
    --BMD
Working...
X