Serious memory leak in Resource in node.js and other environments caused by RequestScheduler.activeRequests

The Issue

When using sampleTerrainMostDetailed often (thousands of times), the memory usage slowly rises.

Inspections

In node this leads to a large external memory usage over time. We managed to replicate the problem in the browser (see this sandcastle gist). This leads to the following profile over 90 seconds:

For some reason, the listeners keep on rising, we are currently trying to get to the bottom of this and would welcome any input.

[jbo023]

@shunter Thanks, when i add RequestScheduler.update() after each sampleTerrain call the memory footprint keeps stable. Maybe this could be documented for methods which can be used without the render loop?

[mramato]

I somehow missed this issue the first time around but @kring just ran into it.

Couldn’t we just have RequestSchedule run update on itself no more than once a frame? Rather than installing a constant even into the event loop, we could have it use process.nextTick and only install the one time handler after a request has resolved.

I may not be explaining it well, but I think this is an easy fix.