{"id":105136,"date":"2022-09-19T21:36:45","date_gmt":"2022-09-19T19:36:45","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/facebook-otkryl-kod-frejmvorka-dlya-vyyavleniya-utechek-pamyati-v-javascript"},"modified":"2022-09-19T21:36:45","modified_gmt":"2022-09-19T19:36:45","slug":"facebook-otkryl-kod-frejmvorka-dlya-vyyavleniya-utechek-pamyati-v-javascript","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/facebook-otkryl-kod-frejmvorka-dlya-vyyavleniya-utechek-pamyati-v-javascript","title":{"rendered":"Facebook has opened the source code for the framework to detect memory leaks in JavaScript.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Facebook (banned in the RF) has released the source code for the memlab toolkit, designed for analyzing snapshots of the state of dynamically allocated memory (heap), identifying optimization strategies for memory usage, and detecting memory leaks that occur when executing JavaScript code. The code is open under the MIT license. <\/p>\n
The framework was created to investigate the causes of high memory consumption when working with websites and web applications. For example, memlab was used to analyze memory consumption with the new version of facebook.com, which revealed leaks that led to browser crashes on the client side due to exhausted free memory. <\/p>\n
Memory leaks when executing JavaScript code can be caused by hidden references to objects, which prevent the garbage collector from freeing the memory occupied by the object, unreasonable caching of values, or the implementation of infinite scrolling without removing older elements from the list. For example, in the code below, in Chrome, a memory leak occurs because of the object «obj», despite it being assigned a value of null, as Chrome maintains internal references to displayed objects to allow subsequent inspection in the web console. var obj = {}; console.log(obj); obj = null; <\/p>\n
Key features of memlab: <\/p>\n
\n
Detection of memory leaks in the browser. Memlab allows for automatic comparison of snapshots of dynamic memory state, detecting memory leaks, and aggregating results.\n
Object-oriented API for traversing the heap, allowing the implementation of custom leak detection algorithms and systems for analyzing heap state snapshots. Heap analysis is supported for browsers based on the Chromium engine, as well as for Node.js, Electron, and Hermes platforms.\n
Command-line interface and API for finding opportunities to optimize memory usage.\n
A system of asserts for Node.js that allows for creating unit tests and running Node.js-based programs to generate snapshots of their own state, check their memory, or write extended assert checks. <\/ul>\n