Potential infinite loop when inserting setting up missing rings.

[mmunro-ltrr]

When someone enables the option to insert missing rings in the simulated core, this happens where the master chronology has small indices (below a hard-coded threshold of 0.6). Consecutive missing rings are possible if there are consecutive small indices, and there's a loop to handle this, which increments an independent index recording how many rings should be skipped over when making up the core, and advances to the next year in the master by adding this count to the index into the array of master indices. There's an additional constraint that the missing ring should not fall on the start or the end of the simulated core, expressed by the condition at

skeleton-plot/SkeletonPlot.js

Line 1081 in 67a30b2

else if (year > Math.floor(coreStart*index.length) && year < Math.floor(coreStart*index.length) + appSettings.rings - 1 ){

Unfortunately if this condition does exclude a missing ring, it also prevents the advance to the next ring, so the loop never terminates. This happens relatively frequently (a few percent of new simulated cores when absent rings are allowed) and is fairly drastic (it depends on the particular Javascript environment, but can cause the user's browser to freeze up).