Tool leads to memory leakage about three-devtools

[jsantell]

Thanks for the detailed report! I'll check it out

[kroko]

In that case, you might be able to put __THREE_DEVTOOLS__ = null at the top of your script to disable it on a specific page -- does this only happen when thousands of renderers are created?

Setting to null will not work.

/* global __THREE_DEVTOOLS__ */
if (typeof __THREE_DEVTOOLS__ !== 'undefined') {
  __THREE_DEVTOOLS__ = null; // eslint-disable-line no-global-assign
}

In strict mode will fail with a bang

Uncaught TypeError: Cannot assign to read only property '__THREE_DEVTOOLS__' of object '#<Window>'

In non strict will probably fail silently.

[jsantell]

via mrdoob/three.js#18759, this looks like it was an issue with a large amount of renderers, an edge case with three.js -- closing this issue for now