等待PDB关闭在一个系统上花费1分钟，在另一个系统上花费5秒钟 [英] Wait PDB close takes 1 minute on one system, 5 seconds on another

问题描述

在我的主开发系统上，链接一个项目需要将近一分钟，而在其他系统上则不到10秒。问题是有关于外部第三方lib找不到lib.pdb的+400警告。管道标准输出与
文件没有区别，并且/时间显示所有时间花费在"等待PDB关闭"：

等待PDB关闭总时间= 57.35324s

在一个表现良好的系统上，对于完全相同的项目，这个时间是5.756秒。两个系统都有SSD，2.5Gz SandyBridge和IvyBridge处理器。

我尝试卸载MSVC 2010并重新安装。这使得时间减少到30秒。然后我尝试安装MSVC 2012.这让时间回到了一分钟。然后我完全卸载了MSVC 2010.现在是57秒。 

这太令人沮丧了。我很想从头开始重新安装Windows，即使这是一个非常全新的安装。 

任何可能出现问题的想法？

解决方案

你好，

 

感谢您的反馈，我将邀请更多专家对其进行调查。

 

祝你好运，

杰西

On my main dev system, linking one project takes close to a minute, while on other systems less than 10 seconds. The problem is that there are +400 warnings about lib.pdb not found for an external 3rd party lib. There is no difference piping stdout to a file, and /time shows that all the time is spent "Wait PDB close":

Wait PDB close Total time = 57.35324s

On a well behaved system, this time is 5.756s for exactly the same project. Both systems have SSD, and 2.5Gz SandyBridge and IvyBridge processors.

I tried uninstalling MSVC 2010 and reinstalling. This brought the time down to 30 seconds. Then I tried installing MSVC 2012. That brought the time back up to a minute. Then I uninstalled completely MSVC 2010. Now it's 57 seconds. 

This is so frustrating. I am tempted to re-install Windows from scratch even though this is a pretty fresh install. 

Any ideas where the problem could be?

解决方案

Hello,

 

Thanks for your feedback, I will involve more experts to investigate it.

 

Best regards,

Jesse

这篇关于等待PDB关闭在一个系统上花费1分钟，在另一个系统上花费5秒钟的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！