Any thought on what might case `infinite rendering invalidation detected` errors in `renderer.js`?

@Dan_Monroe wrote:

RWJBlue says,

basically what is happening is that something is throwing an error during rendering

(this should be “ok”, and print the error to the console for you to fix)

when an error occurs during rendering, we cleanup the current rendering transaction (an attempt to avoid other issues when further rendering is needed

however, part of our cleanup for the current transaction is to call didInsertElement and didRender for the things that did get rendered (before the error was thrown)

unfortunately, if you have things that always do a this.set in didInsertElement or didRender then this causes another rendering loop before “settling”

the renderer starts the rendering loop again, but hits the same error as it did the last time

during cleanup of that error the didInsertElement / didRender is called, forcing another render, that render throws, didInsertElement / didRender is called, forcing another render, render throws,

infinite rendering detected

to be clear this is only one possible reason for the infinite rendering detection error, its possible that you actually have a legit bug in the app code that is causing it (edited)

a legit instance of this error would be doing something like this.set('someValueUsedInTemplate', Math.rand()) in didRender (since a new random value is always used, every render triggers another render)

Posts: 1

Participants: 1

Read full topic