High utilization after opening aspx.cs files

Hello Jonathan,

does the method whose usages you were searching have many usages? And is
its name
common (e.g. Run or ToString)?

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Using Find Usages to retrieve references to a method I'm trying to
refactor out of existence, I opened one of the pages that consumes the
DAL method I'm trying to kill, then called Find Usages again to
confirm the usages of the method I was then reworking.

Memory consumption on our 22 project solution went to 420M, and cpu
utilization spiked to 90+%. Below is the ProcExp stack for the thread
consuming 80%+ of cpu utilization most of the time:

ntdll.dll!KiFastSystemCallRet
mscorwks.dll!DllUnregisterServerInternal+0x47b1
mscorwks.dll!DllUnregisterServerInternal+0x477a
mscorwks.dll!DllUnregisterServerInternal+0x4730
mscorwks.dll!TranslateSecurityAttributes+0x277e6
mscorwks.dll!CreateApplicationContext+0xc4a7
kernel32.dll!GetModuleFileNameA+0x1b4
Attaching to the identified high-utilization thread gives this call
stack: (hmm, as reported elsewhere, copying the stack hangs both
instances of devenv.exe). The call stack showed a very deep call stack
in mscorwks.dll...

Three usages, and quite distinct method name (FetchDirectorNames)

From the stack traces, it seems like maybe probing the ASPX file to get the
control objects for the code-behind is getting into a loop.

"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d9112bae8c809fc2ff08b89@news.intellij.net...

Hello Jonathan,

>

does the method whose usages you were searching have many usages? And is
its name
common (e.g. Run or ToString)?

>

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>
>> Using Find Usages to retrieve references to a method I'm trying to
>> refactor out of existence, I opened one of the pages that consumes the
>> DAL method I'm trying to kill, then called Find Usages again to
>> confirm the usages of the method I was then reworking.
>>
>> Memory consumption on our 22 project solution went to 420M, and cpu
>> utilization spiked to 90+%. Below is the ProcExp stack for the thread
>> consuming 80%+ of cpu utilization most of the time:
>>
>> ntdll.dll!KiFastSystemCallRet
>> mscorwks.dll!DllUnregisterServerInternal+0x47b1
>> mscorwks.dll!DllUnregisterServerInternal+0x477a
>> mscorwks.dll!DllUnregisterServerInternal+0x4730
>> mscorwks.dll!TranslateSecurityAttributes+0x277e6
>> mscorwks.dll!CreateApplicationContext+0xc4a7
>> kernel32.dll!GetModuleFileNameA+0x1b4
>> Attaching to the identified high-utilization thread gives this call
>> stack: (hmm, as reported elsewhere, copying the stack hangs both
>> instances of devenv.exe). The call stack showed a very deep call stack
>> in mscorwks.dll...
>>
>