clr.sll!StrongNameSignatureVerification CPU消耗 [英] clr.sll!StrongNameSignatureVerification CPU consumption

查看:113
本文介绍了clr.sll!StrongNameSignatureVerification CPU消耗的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个C#(.NET 4.0)WinForm应用程序,该应用程序不断与基于Linux的应用程序进行通信,每秒从其接收一些数据.当我看到" clr.sll!StrongNameSignatureVerification "正在为此应用程序消耗大量CPU时,我一直在对该WinForm应用程序进行微调,以减少它的高CPU使用率.我使用Process Explorer找出了这一点.一些Google搜索告诉我"clr.sll!StrongNameSignatureVerification"正在启动,因为CLR试图验证这是否是一个重命名的程序集(我不希望CLR这么做).

I have a C# (.NET 4.0) WinForm application that continuously communicates to a Linux based application, receives some data from it few times a second. I have been fine-tuning this WinForm application to reduce it's high CPU use when I saw 'clr.sll!StrongNameSignatureVerification' is consuming a lot of CPU for this application. I used Process Explorer to find this out. Some Google searching told me that 'clr.sll!StrongNameSignatureVerification' is kicking-in because CLR is trying to verify whether this is a strongly named assembly (which I don't want CLR to).

在对此进行进一步研究之后,我尝试使用Microsoft SDK中的 sn.exe 跳过此WinForm应用程序的签名验证.我收到一个错误消息,说这不是一个重命名的程序集. 我没有为这个应用程序签名,或者不记得设置任何应调用CLR来验证该应用程序签名的功能,这并不令我感到惊讶.

After my further research on this, I tried sn.exe from Microsoft SDK to skip signature verification for this WinForm application. I got an error saying that this is not a strongly named assembly. I wasn't surprised as I haven't signed this application or don't remember setting anything that should invoke CLR to verify the signature of this application.

我在.net应用程序安全方面的经验几乎为零,因此此刻我正在寻求一些帮助.任何指针都会有所帮助.

My experience in .net application security is almost zero so at moment I am looking for some help on this matter. Any pointer will be helpful.

谢谢.

推荐答案

查看 clr.sll!StrongNameSignatureVerification后的偏移量,如果该偏移量大于几千个字节,则可能表示符号是没有加载到Process Explorer中,并且问题可能出在 clr.dll中的任何其他方法中.

Look at the offset after clr.sll!StrongNameSignatureVerification, if it's larger than a few thousand bytes, it probably means the symbols are not loaded in Process Explorer and the problem might be in any other method in clr.dll.

这篇关于clr.sll!StrongNameSignatureVerification CPU消耗的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆