Still seeing 95% "Native or optimized code" in IIS7 using dotTrace 5.3.1

Dear Steven,

I think you use 64-bit mode in your IIS7. Could you check that you haven't got the following warning in the controller window: "Failed to apply patch for CLR vX.0 x64"?
I redesigned the patcher in dotTrace 6.0 to make it universal. Now we have a discusion to include new patcher into dotTrace 5.X.

WBR,
Mikhail Pilin

I don't see a warning in the controller window, but not sure if I'm looking in the right place or at the right time. Here's what I'm seeing:



The initial progress window that briefly comes up flashes a bunch of steps, including something about profiler cores, but I don't think I see any error or warning messages there. Is there a log file I can look at?

Dear Steven,

That's great! Could you please send me core logs?

Please do the following:

1. close standalone dotTrace and Visual Studio with integrated dotTrace.
2. go to your Temp folder (you can find its location by executing 'cd %Temp%' in command line).
3. find 'JetLogs' folder and delete it.
4. launch dotTrace, prepare for profiling; in 'Profiler Configuration' dialog, press Ctrl + Shift + Alt + F11.
5. click 'Expert options' button.
6. enable 'Enable logs' checkbox and MetaDataGt, PerformanceSamplingGt checkboxes
7. click OK and run profiling.
8. perform actions that lead to issue.
9. close dotTrace.
10. send content of %Temp%/JetLogs to me.

Mikhail -

Have this problem been resolved?  I'm running an evaluation copy of the product and I'm experiencing the same issues as Steven.

Thanks.

Tim

Dear Tim,
I don't exclude that the issue is still presented in some computer configuration because MS generates updates for OS, CLR, IIS, ... So, I always ready to investigate the every new problem. Are you ready to help me? Could you please send me core logs in that case (see the instruction above)?
WBR,
Mikhail Pilin

Dear Tim,

Thank you for logs. You have warning: "Failed to apply patch for CLR v4.0 x64". It means that our patcher detect incompatible CLR version. I already have the fix (for dotTrace 6.0). However, I need one-two days to approve it for dotTrace v5.3.1.

Hi,

I have the same issue here I'm using build 5.3.1114.16
windows 2008 standard 64 bit w3wp process running in x64 mode


I'm try to attach to the process and after I get a snapshot I get 99 percent of my threads i see a message native or optimized code

Can I help do resolve this issue?

Hello Geoffrey, please contact me (alexandra.rudenko@jetbrains.com), and I'll send you a custom build with the fix.

Hi,
I'm also seeing a similar issue with the current evaluation version, has this problem been rectified, or is it still present?

I'm using remote profiling on .Net 4.5.50709 on Windows Server 2008 R2 (64 bit)

Regards,
Tom

Dear Tom,

100% "Native or optimized code" for all managed threads is correct for some usage scenario (attach to w3wp.exe and immediately get snapshot) because IIS is native application which sometimes calls managed code. So, please add some activity into your scenario and you see managed code in snapshot.

I belive that the last dotTrace works perfectly because the last issue was solved a month ago for v5.3.2. However, I'm ready to investigate your problem if you have a time.

--
Mikhail Pilin
Senior Software Engineer
JetBrains GmbH
http://JetBrains.com
"Develop with pleasure!"

Ah right, looks like I am using 5.3.1, so that may well be the cause of the problem. Is 5.3.2 available for download anywhere?

Thanks,
Tom

Dear Tom,

I sent the link to you by mail.

--
Mikhail Pilin
Senior Software Engineer
JetBrains GmbH
http://JetBrains.com
"Develop with pleasure!"