Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

196
Views
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
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!