Home/ Questions/Q 8102185
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-05T23:10:51+00:00

I’m getting an Aw, snap! chrome crash when a certain webpage is being loaded.

  • 0

I’m getting an “Aw, snap!” chrome crash when a certain webpage is being loaded. I’m trying my best to figure out what’s causing it and having a really hard time.

In the Chrome Developer’s tool there is a Memory Tab and when looking at the counter graphs, I notice that the DOM Node Count line steps up, drops, and then continues to rise.

Dom node count increasing

I understood this to mean that the DOM element counts on my page were increasing but after doing 

document.getElementsByTagName("*").length

in the console I noticed the value wasn’t changing.

So what is the DOM Node count graph actually showing? If it continues increasing like this, could that potentially be the cause of the “Aw, snap!” crash?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The DOM node count graph shows the number of created DOM nodes that are still held in memory, i.e. which have not been garbage collected yet. This doesn’t have to coincide with the elements you get through getElementsByTagName. The latter will also only get you the elements actually attached to the document tree. It won’t get any ‘offline’ items to which you still have references.

    An easy way to get stuck with this particular pyramid growth is the Like widget from the Facebook API, which contains some code on a run-away timer that creates boatloads of additional DOM nodes.

    • 0