Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

TypeError null is not an object (evaluating 'elt.parentNode')

See original GitHub issue

I have started getting some error reports in Sentry from our JS app which look like this:

TypeError null is not an object (evaluating 'elt.parentNode')

Problem is, that nowhere in our own source code, nor in our vendor source code, can I find a single instance of elt.parentNode in the code.

Also, Sentry seems to have a hard time reporting the source of the error as well:

TypeError: null is not an object (evaluating 'elt.parentNode')
  at ? (/shop/kleding/new-arrivals/fresh/donkerblauw:1:350)

This doesn’t actually point to any JS code, just the rendered HTML of our SPA. And in the breadcrumbs, it just gets repeated several times:

In short, I have no idea where this error is coming from, and I am suspecting it might be generated by Sentry itself somehow, as I can’t find any references to it in our own code.

Any suggestions on how to analyse this further and/or rule out Sentry/ravenjs as the source of this issue?

Issue Analytics

State:
Created 7 years ago
Comments:44 (6 by maintainers)

Top GitHub Comments

53reactions

benvinegarcommented, Jan 26, 2017

So, getsentry/sentry#4823 is now merged, which means that as soon as it deploys (within hours), you can enable the “Filter out errors known to be caused by browser extensions” inbound filter to filter/suppress this error. It will not count towards your quota.

You can find this at: Project → Project Settings → Inbound Filters