JavaScript memory leaks
Reported by
quake314...@gmail.com,
Aug 25 2016
|
|||||
Issue descriptionChrome Version: 52.0.2734.116 OS: Windows 10 64-bit <b>See <http://www.chromium.org/for-testers/providing-memory-details> to</b> provide memory usage snapshots. URL (if applicable) where the memory bloat occurred: ch.gswtech.com.pl Can you reproduce this memory bloat? Open the website and wait. What steps will reproduce this memory bloat (or if it's not reproducible, what were you doing until then)? (1) Go to the above URL (test site) (2) Wait a couple of hours (3) The memory gradually rises I need to display a website using an embedded chromium, which will be running at least 12 hours a day. During tests I noticed huge memory leaks. When left for the night chrome has been using up to (and over) 2GB of RAM, which eventually causes process to crash. There is only JavaScript running on the test page.
,
Aug 29 2016
After a first, quick look: It is not creating new dom elements on the fly without end. We should have a look at it. No clue if it is V8 or Blink memory related though.
,
Aug 31 2016
jQuery.now() Is creating lots of new Date()'s That is the source of the leak. It should use Date.now() instead.
,
Oct 18 2016
Matthias said, "jQuery.now() Is creating lots of new Date()'s" ... Is there a bug in the Date object? No matter how rapidly it is called, such objects should be automatically garbage-collected, like any JavaScript object. Indeed, it is very common for JavaScript code to frequently invoke ((new Date()).getTime()) to get an integer timestamp value, and I have never seen a leak caused by that code. On the other hand, if the page's code is assigning the Date objects into an array or structure, and that array is constantly growing, then the page could begin to use a great deal of memory, but it is still not really a "leak", because the memory will be recovered when the browser navigates to another page (and the prior page's memory is freed). Has anyone noticed what happens when the browser is then navigated to "about:blank"? Is the memory freed?
,
Aug 2 2017
This bug is available, yet hasn't been updated in >180 days. Dropping the priority.
,
Aug 3
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 7
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by tkonch...@chromium.org
, Aug 26 2016Components: Blink>JavaScript
Labels: -Pri-3 M-54 OS-Windows Pri-2 Type-Bug
Status: Untriaged (was: Unconfirmed)
145 KB
145 KB View Download