TypeError: Cannot read property 'template' of null

[jcbvm]

Since 1.13.3 I get the following error which seems to be thrown somewhere deep in htmlbars TypeError: Cannot read property 'template' of null. Is this a known problem? If not, I have to investigate further where this is coming from.

Stacktrace:

TypeError: Cannot read property 'template' of null
    at Ember.Object.extend._nodeTemplateName (<anonymous>:4122:43)
    at Ember.Object.extend._shouldShowNode (<anonymous>:3978:17)
    at <anonymous>:3949:18
    at Array.forEach (native)
    at Ember.Object.extend._appendNodeChildren (<anonymous>:3948:18)
    at <anonymous>:3954:16
    at Array.forEach (native)
    at Ember.Object.extend._appendNodeChildren (<anonymous>:3948:18)
    at Ember.Object.extend.viewTree (<anonymous>:3597:14)
    at <anonymous>:3553:25

[btecu]

I've been randomly getting this. Can't find what the issue is.

[rwjblue]

I don't recall another issue for this, thank you for reporting.

I have to investigate further where this is coming from.

👍 - To track this down we will need a reproduction.

[jcbvm]

Will look further into it.

[btecu]

Looks like when in Firefox the error is renderNode.lastResult is null.
Still, I don't know yet what's causing it.

[jcbvm]

It seems like a timing issue, because the error pops up randomly, looks to me if it's trying to update the DOM which isn't existing anymore.

[btecu]

That's what my guess was too, but it looks like the cause of my problem is ember inspector.
The issue seems to happen if I go at least once to the ember inspector tab. I'll get the errors immediately and every time I refresh or navigate until I close that page (doesn't matter if I change the tab in development tools). I never get this issue in IE - and now I understand why - because there is no ember inspector for IE.

@jcbvm can you check if this is the problem for you too?

[jcbvm]

@btecu Ah, that's interesting, will look at it tomorrow when I have access to the code. Will let you know.

[rwjblue]

@teddyzeenny - Is this something you have seen before?

[teddyzeenny]

Yes. The error is now guarded against in emberjs/ember-inspector#417. Not yet released.

[rwjblue]

@teddyzeenny - Awesome, thank you!

@jcbvm - I'm going to close this issue, as this is fixed upstream...

[jcbvm]

Glad to know the cause of the problem, thanks all for helping.