DotTrace Timeline fails 90% of the time, even with --local_crl

Avatar
E Hasanaj
Created

Honestly really frustrating, I can't seem to get rid of this problem. 
I set up ETW in my server and start it with --local_crl, and then start dottrace (either command line or GUI), but 90% of the time it fails with “Command timeout”. 
I would appreciate some help because right now its completely unusable 

Votes

0

Share

4 comments
Avatar
Anna Guseva
Created
Official comment

Hi!

Could you please provide us with ETW.Collector logs:

  • Clear %temp%\JetLogs and %systemroot%\Temp\JetLogs folders
  • Kill JetBrains.ETW.Collector.exe and JetBrains.ETW.Collector.Host.exe processes and restart ETW Service
  • Restart dotTrace
  • Reproduce the issue
  • Send us both the %temp%\JetLogs and %systemroot%\Temp\JetLogs folders with all log files


We also need the next information:

  • Windows version
  • Are there any crashes logged in Windows Event Viewer?

You can upload log files to our ftp.

 

Avatar
E Hasanaj
Created

Hey there,

Also today I am trying to get a timeline snapshot, and again ive had 10+ unsuccessful tries, so thanks for picking this up for me.

I did the steps mentioned, and uploaded the files at: Upload id: 2025_11_14_Pyfz7AyRfi4o5yBovjkVkq (file: LOGS.zip)

I am doing this on a Windows Server 2016 Standard
And there seem to be no crashes in Event Viewer

0
Avatar
E Hasanaj
Created

Any updates here? Still same problems, still I have to be really lucky to be able to get a profiling session to work…

0
Avatar
Anna Guseva
Created

Hi!

Sorry for the delay.

This is a known issue related to the fact that “--local_crl” parameter is not considered in one place of code. 

Unfortunately the fix hasn't been released yet and there is no workaround available.

We will notify you when the fix becomes publicly available.

0

Please sign in to leave a comment.