reduced how often collect cycles is called

[clinuxrulz]

regards #77

[clinuxrulz]

Note: jest is only working on an older version of node at the moment.
jestjs/jest#8069

So you can ignore the jest errors, all tests pass here.

[clinuxrulz]

Hold off merging this one. Problem still not resolved when I trial this code. I'm going to investigate some more.

[clinuxrulz]

This PR is all good. I did some further investigation and it was actually calling collectCycles just once per transaction at most (less than once per transaction if no decrements occur). It was just the nature of the code I've written for that incremental update of three.js code, there are transactions occurring in that code when wiring up independent parts to the actual scene giving the illusion of many collectCycles in one transaction, when in fact it was one collectCycles in each of many transactions. (The 3d model construction code was passing over an asynchronous boundary, for use such as fetching the textures for the model causing many transactions.)

[the-real-blackh]

Are you missing some commit privileges?

[clinuxrulz]

No. I just like having a 2nd set of eyes to review what I do, just in case I make a mistake.

[clinuxrulz]

In the Travis log file I can see:
"Skipping a deployment with the npm provider because this is not a tagged commit"

Does that mean someone here has done CI? And we just need to tag the commit in order to get a new version on npm?