In CommunicationLoadBalanceGrids, there's a loop over ProcessorComputeTime to find the min and max of that array. Periodically, the minimum of the array is larger than the original guess for the minimum, "huge_number." When this happens, the code fails, because a suitable minimum processor cannot be found.
This mod first finds MaxVal, the maximum of the array, and then uses it as the initial guess for MinVal. This ensures a minimum can always be found. (Also removes the comment claiming it was fixed in 2005, as the comment survived but the fix did not. )