Empresas
Empleos
  • Sobre nosotros
  • Soluciones
    • Publicación de vacantes
      Publica tu vacante y recibe candidatos calificados en 48h.
    • Evaluación de candidatos
      500+ pruebas técnicas y psicológicas, más anti-fraude.
    • Headhunting
      Búsqueda ejecutiva a la medida de principio a fin.
    • Nómina + EOR
      Dispersión de nómina y EOR en más de 15 países de LATAM.
  • Precios
  • Empleos

0

205
Vistas
How to interpret memory dump in chrome developer tools

I am trying to find a memory leak (in my electron app). Amongst other things I tried to interpret a memory dump. Now I wonder about a couple of things:

  1. Is it normal that the application code is stored as string in memory? I wonder especially because there is an extra line below (see 2nd screenshot) listing "compiled code", also occupying memory. Shouldn't the js-strings be cleaned from memory as soon as it's loaded into a data structure? enter image description here

  2. I see that some objects are alocating a lot of space, but I don't understand the "Retainers" list. There is a lot of webpack and hot update stuff which seems to reference those objects. How can I distinguish "good references" from "bad references"? enter image description here

about 4 years ago · Juan Pablo Isaza
Responde la pregunta
Encuentra empleos remotos

¡Descubre la nueva forma de encontrar empleo!

Top de empleos
Top categorías de empleo
Empresas
Publicar vacante Precios Comercial
Legal
Términos y condiciones Política de privacidad
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Recomiéndame algunas ofertas
Necesito ayuda