Haddii ka dib markaad u cusboonaysiiso Windows 10 ama .NET Framework 4.7.1 , oo aad aragto hoos u dhac weyn oo ku yimaada waxqabadka markaad maamulayso .NET Framework codsiyada isticmaala fasalka System.Diagnostics.StackFrame , ka dibna boostada ayaa laga yaabaa inay xiiseyneyso. Waxaan eegi doonaa sababta, ka dibna waxaan bixin doonaa hagaajin la yaqaan ee qaladka.

Nidaamka.Diagnostics.StackFrame waxqabadka hoos u dhaca

Codsiga lahaa waxqabadka la aqbali karo ee ku socda .NET Framework 4.7 ama noocyadii hore ayaa si tartiib tartiib ah u fuliya marka uu ku socdo .NET Framework 4.7.1 . Codsiyada sida caadiga ah waxay ku tiirsan yihiin StackFrame marka ay tuurayaan .NET ka reebban. Haddii ay tani ku dhacdo xawaare sare (in ka badan 10 shil ilbidhiqsikii), arjiyada ayaa si weyn hoos u dhigi kara (toban laab) oo si muuqata uga gaabiya sidii hore.

Sababta Nidaamka.Diagnostics.StackFrame waxqabadka hoos u dhaca^{(Cause of the System.Diagnostics.StackFrame performance degrade)}

Qaab dhismeedka .NET Framework 4.7.1^{(.NET Framework 4.7.1)} gudaha Windows 10 wuxuu ku daray taageerada ogaanshaha iyo kala shaandheynta qaabka faylka PDB ee la qaadi karo si loo muujiyo faylka iyo macluumaadka lambarka khadka ee raadadka taranka. Iyada oo qayb ka ah isbeddelkan, hawl kasta oo ku jirta raad-raac raso waxa ay leedahay cutubka qeexaya ee la hubiyay si loo go'aamiyo haddii cutubkaas uu isticmaalo qaabka PDB ee la qaadi karo . Sababo^(Due) la xiriira qaar ka mid ah kala duwanaanshiyaha siyaasadda kaydinta gudaha, runtime waxay ku bixisaa waqti aad uga badan raadinta PDB-yada la qaadi karo^{(Portable PDBs)} marka loo eego noocyadii hore ee NET Framework ee lagu raadin jiray Windows PDB-yada^{(Windows PDBs)} caadiga ah .

Tani waxay sababtaa in raad-raacyo habaysan loo soo saaro si tartiib tartiib ah sidii hore.

Arrinkani ma beddelayo tirada ka reebban ee la tuuray. Si kastaba ha ahaatee, waxay si weyn u dhimaysaa awoodda codsiyada si ay wax uga qabato waxyaabaha ka reeban.

Codsiyada adeegsada maktabadda IKVM waa la og yahay inay arrintan saameynayso haddii ay baaraan shirarka. Baaritaanka shirarka waa la og yahay inay keento ka-reebis.

Hagaaji System.Diagnostics.StackFrame^{(Fix System.Diagnostics.StackFrame)} waxqabadka hoos u dhigaya arrinta

Si arrintan loo xalliyo, Microsoft waxay ku talinaysaa in la isticmaalo mid ka mid ah hababka soo socda.

1] U isticmaal dhise ka duwan StackFrame kaas oo qaata doodda Boolean^{(1] Use a different constructor for StackFrame that takes a Boolean argument)}

Tani waa xalka la door bidayo.

Haddi horumariyeyasha arjiyada ay awoodaan inay isbedel ku sameeyaan codsiyadooda, wac ^{(call the)} System.Diagnostics.StackTrace. #ctor ( Boolean ) dhise isagoo isticmaalaya dood been abuur ah si uu uga fogaado qabashada macluumaadka isha. Tani waxay ka fogaanaysaa qaybta koodka ee waxqabadka la dhimay.

2] Dib-u-soo-celinta ama u cusboonaysii nooca ugu dambeeyay ee Windows 10^{(2]  Rollback or upgrade to the latest Windows 10 version)}

Habkan, dib ugu laabo noocii hore/dhis ama upgrade to the latest version/build  Windows 10^{(Windows 10)} haddii aad la kulanto arrintan oo aanad hadda ku shaqaynayn noocii ugu dambeeyay ee Windows 10 . Sidoo kale uninstall .NET Framework 4.7.1 haddi ay jirto, ka saar kombayutarka ka dibna soo^(download) deji oo ku rakib nooc hore ama noocii ugu dambeeyay ee .NET Framework .

Hope this helps!

System.Diagnostics.StackFrame performance degrade in Windows 10

If after уou upgrade to Windows 10 or .NET Framework 4.7.1, and you notice a significant decrease in performance when you run .NET Framework applications that use the System.Diagnostics.StackFrame class, then this post might interest you. We will look at the cause, and then offer known fixes for the error.

System.Diagnostics.StackFrame performance degrade

An application that had acceptable performance running on the .NET Framework 4.7 or earlier versions executes more slowly when running on the .NET Framework 4.7.1. Applications typically rely on StackFrame when they throw .NET exceptions. If this occurs at a high rate (more than 10 incidents per second), applications can slow down significantly (tenfold) and run noticeably slower than before.

Cause of the System.Diagnostics.StackFrame performance degrade

The .NET Framework 4.7.1 in Windows 10 added support for detecting and parsing the Portable PDB file format to show file and line number information in stack traces. As part of this change, each function in a stack trace has its defining module checked to determine if that module uses the Portable PDB format. Due to some differences in the internal caching policy, the runtime spends far more time searching for Portable PDBs than previous .NET Framework versions spent searching for classic Windows PDBs.

This causes formatted stack traces to be produced more slowly than before.

This issue does not change the number of exceptions that are thrown. However, it does significantly decrease the ability of applications to handle those exceptions.

Applications that use IKVM library are known to be affected by this issue if they probe for assemblies. Probing for assemblies is known to cause exceptions.

Fix System.Diagnostics.StackFrame performance degrade issue

To resolve this issue, Microsoft recommends using either of the following methods.

1] Use a different constructor for StackFrame that takes a Boolean argument

This is the preferred solution.

If application developers are able to make changes to their applications, call the System.Diagnostics.StackTrace.#ctor(Boolean) constructor by using a false argument to avoid capturing source information. This avoids the section of the code in which performance is decreased.

2]  Rollback or upgrade to the latest Windows 10 version

In this method, roll back to the previous version/build or upgrade to the latest version/build of Windows 10 if you’re experiencing this issue and you’re not currently running the latest version of Windows 10. Also uninstall .NET Framework 4.7.1 if present, from your computer and then download and install a previous version or the latest version of .NET Framework.

Hope this helps!

Related posts

• Sida loo hubiyo .NET Framework nooca lagu rakibay Windows 10 PC

• Hagaaji qaladka 0x800F080C markaad ku rakibayso NET Framework Windows 10

• Dooro meesha aad ka heli karto ikhtiyaarka abka Windows 10 Settings

• VPN ku salaysan CMAK ma shaqaynayo Windows 10 ka dib

• Cloud Clipboard (Ctrl+V) oo aan shaqaynayn ama ku shaqaynayn Windows 10

• SID waxay muujisaa halkii ay ka ahaan lahayd isticmaale ama magac saaxiibtinimo gudaha Windows 10

• Caawinta degdega ah ma shaqaynayso; Ku dheggan soo dejinta ama ku xidhidhiyaha Windows 10

• Daaqadaha ayaa dhamaystiri kari waayay isbeddelada la codsaday

• Software-ka ugu fiican ee Barcode Scanner ee bilaashka ah ee Windows 10

• MSVCR71.dll ayaa ka maqan Windows 10 kumbuyuutarka

• Cilad-ka-hortagga Windows 10 Barafka ama Quful si aan kala sooc lahayn

• Cilad-bixinta daabacaha oo ku dheggan Xaaladda qadla'aanta ee Windows

• Kumbuyuutarku si khaldan ayaa loo ogaaday inuu ka baxsan yahay shabakada internetka

• Hagaaji server-ka RPC waa qalad aan laga heli karin gudaha Windows 10

• Qaabka diyaaraduhu ma dami doono gudaha Windows 10

• Cilad-bixinta Windows 10 Ma Tago Hurdo

• Sida loo isticmaalo Network Sniffer Tool PktMon.exe gudaha Windows 10

• Khaladaadka Xogta Cusbooneysiinta ee suurtagalka ah ee Windows 10

• Waxaad u baahan tahay ogolaansho si aad falkan ugu qabato Windows 10 [Fixed]

• Wararka iyo xiisaha aan ka muuqanayn ama ka maqan Windows 10