You guys have a memory leak on the challenges page. Leaving the page open and active uses a lot of CPU and ever increasing amounts of memory. Tested in Firefox and Chrome, Windows 8 and OSX.
I assume this is because your Javascript is trying to update the "time remaining" DOM elements several hundred times per second, and not simply once per second.
0
Memory Leak On Challenges Page
Started by Xadhoom, Feb 12 2016 02:32 PM
1 reply to this topic
#2
-
-
- Little Helper
- 4,247 posts
Member
- LocationUnknown... Except for the stars, it's kind of dark here!
Posted 13 February 2016 - 08:58 PM
No wonder MWO keeps getting dragged down when I've had that page open and visible in the browser. I usually end up burying it under another tab in order to stop the CPU drain, but it comes right back the moment I forget to do so before launching into a match. 
Argh. *facepalm* PGI, please fix A.S.A.P.!
~D. V. "Well, this answers my wonder of what was happening!" Devnull
Argh. *facepalm* PGI, please fix A.S.A.P.!
~D. V. "Well, this answers my wonder of what was happening!" Devnull
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users
