Zwill Posted September 25, 2018 Share Posted September 25, 2018 NAME: memory leak SEVERITY: 3/2(could impact lower end systems) LOCATION: physical memory REPRODUCIBILITY: always DESCRIPTION: after a few weeks of playing (mostly relogging and trying again or force closing when it freezes, which is fair right now) my systems idle physical memory has risen from 20% to 72% (16 GB). I hibernate my computer at night so this problem hasn't resolved it's self until I restarted today ADDITIONAL INFORMATION: I'm assuming destructors and general stability. just noticed it was happening and didn't see anyone post about it yet. Quote Link to comment Share on other sites More sharing options...
fiki574 Posted September 26, 2018 Share Posted September 26, 2018 Are you positevly sure it's our launcher that's causing those? Because I think that people with lower end PCs would experience this before you and report appropriately. Quote Link to comment Share on other sites More sharing options...
Kenny112 Posted September 26, 2018 Share Posted September 26, 2018 (edited) Hey I can not unfortunately english but through the google translator hopefully ^ ^ have read the post and already noted similar memory my true on about 80% as the game has crashed and I ended it only when I restarted the computer is the problem gone .... Edited September 26, 2018 by Kenny112 Quote Link to comment Share on other sites More sharing options...
Kubik Posted September 26, 2018 Share Posted September 26, 2018 how many times you start the updater in these "few weeks" @Zwill? Quote Link to comment Share on other sites More sharing options...
FkDisGem Posted September 27, 2018 Share Posted September 27, 2018 I have not seen this to be true, must be something else on your pc - or you are misinterpreting the way your OS handles ram. I have had it running in the background now for 30mins and it actually went down by 0.1mb in ram usage. Quote Link to comment Share on other sites More sharing options...
fiki574 Posted September 28, 2018 Share Posted September 28, 2018 I've done some improvements nonetheless, so even if there were existing memory leaks they will be gone after next launcher update (just watch Discord and thats it) Quote Link to comment Share on other sites More sharing options...
Zwill Posted September 28, 2018 Author Share Posted September 28, 2018 @Kubik in the 2 weeks I've probably tried every other day to play and depending on how many times it freezes or crashes probably 20-30 times a day. so roughly 160-240 as a spitball estimate. @fiki574 I don't think it would be anything else as battleforge is the only program I've been using the past few weeks that I don't normally use, I would imagine people with lower end systems don't use hibernate at night and shut it off instead which would fix the problem before it's noticeable. It took 2 weeks(of pretty zealous trying) before I noticed with 16GB so it so it would be 3.5 days of computer uptime for lower end users to notice, this is just speculation though. I just wanted to make sure someone noted it because I hadn't seen a post about it yet. It is probably very small but needing to relaunch the game so much right now is compounding the issue. my coding teacher also drilled into us about not leaking memory so I felt the need to let you know. Keep up the great work @ATRmayo it's not running the game/launcher in the background that's the problem, it's idle system memory after the game has been closed and opened many times. Quote Link to comment Share on other sites More sharing options...
Kubik Posted September 29, 2018 Share Posted September 29, 2018 I normally do not care about "leaking" memory that I need soon after program start, till the end, because OS take care of that memory once the process is closed. So if you close the process all memory leaks are "gone" OS must take care of it. So from the fact you must restarted the game multiple times, there is no way how it could cause your memory issues. I have only 64 GB of RAM and 16 GB of it is RAM disk, and Windows do crap random memory usage, so until we speak about multiple gigabytes I think it is impossible to say, without profiler, that single program causing it. Quote Link to comment Share on other sites More sharing options...
Recommended Posts