功能代码(在与供应商调试问题之后)大致如下：

Task.Factory.StartNew(() => ValidateCalibration(pelRectRaw2Ds,crspFeatures,Calibration.Raw2DFromPhys3Ds));

    .....

    private void ValidateCalibration(List<Rectangle> pelRectRaw2Ds,List<List<3DCrspFeaturesCollection>> crspFeatures,List<3DCameraCalibration> getRaw2DFromPhys3Ds)
    {
        var calibrationValidator = new 3DCameraCalibrationValidator();

        // This is required according to vendor otherwise validationResultsUsingRecomputedExtrinsics is occasionally null after preforming the validation
        GC.SuppressFinalize(calibrationValidator);

        3DCameraCalibrationValidationResult validationResultUsingOriginalCalibrations;
        3DCameraCalibrationValidationResult validationResultsUsingRecomputedExtrinsics;
        calibrationValidator.Execute(pelRectRaw2Ds,getRaw2DFromPhys3Ds,out validationResultUsingOriginalCalibrations,out validationResultsUsingRecomputedExtrinsics);

        Calibration.CalibrationValidations.Add(new CalibrationValidation
            {
                Timestamp = DateTime.Now,UserName = Globals.InspectionSystemObject.CurrentUserName,ValidationResultUsingOriginalCalibrations = validationResultUsingOriginalCalibrations,ValidationResultsUsingRecomputedExtrinsics = validationResultsUsingRecomputedExtrinsics
            });
    }

验证过程是一个相当耗时的操作,所以我把它交给一个任务.我曾经遇到过的问题是,原来我没有调用GC.SuppressFinalize(calibrationValidator),而当应用程序从Release版本运行时,out参数validationResultsUsingRecomputedExtrinsics将为null.如果我从Debug构建运行应用程序(有或没有调试器附加),那么validationResultsUsingRecomputedExtrinsics将包含有效的数据.

我不完全明白GC.SuppressFinalize()在这种情况下所做的事情,或者如何解决问题.我可以找到关于GC.SuppressFinalize()的一切,就是在实现IDisposable时使用它.我在“标准”代码中找不到任何用途.

如何/为什么添加对GC.SuppressFinalize(calibrationValidator)的调用解决了这个问题？

我明白,如果没有对供应商图书馆的内部部分的深入了解,可能无法确定,但任何见解都将有所帮助.

该应用程序使用针对.NET 4.0的VS2012进行编译.该供应商库要求在app.config中指定useLegacyV2RuntimeActivationPolicy =“true”选项.

这是我从供应商那里得到的理由：

The SuppressFinalize command makes sure that the garbage collector will not clean something up “early”. It seems like for some reason your application was sometimes having the garbage collector get a bit zealous and clean up the object before you were truly done with it; it is almost certainly scope related and possibly due to the multi-threading causing confusion on the scope of the calibrationValidator. Below is the response I got from Engineering.

Because the variable was created in the local scope,and that function runs in the background thread,Garbage Collection runs in the main thread,and it seems that the Garbage collection is not smart enough in handling multi-thread situations. Sometimes,it just releases it too early (internal execution of validator not finished yet,and still needs this variable).