Issue with Symbols Lookup with PerfView V1.8 collecting on older OS version


I wanted to blog about this just to increase the visibility of this bug since it may me more common that I thought. 

If you are using Versions 1.8 of PerfView and you are COLLECTING data using PerfView using its default setting and when you look at your resulting .ETL.ZIP file and it gives you a dialog box that says you did not 'Merge' your data (and you can't get any symbols for native/OS dlls to resolve), then you should read further.   If not please ignore this post.

There is a bug with newer code that PerfView uses such that on SOME older OSes (I have not characterized that yet), this effect occurs.

There is a simple work around.  You can use an older version of PerfView (e.g. V1.7) to do the collection (you can still view the data with V1.8).  

You can get the V1.7 version of PerfView from http://1drv.ms/1NHA1HB in the OldPerfviewVersion directory.  

This of course will be fixed in the next version (V1.9) which should be released soon (next few weeks), but in the mean time you have a work-around.

Vance

Comments (7)

  1. Vishnu says:

    Hi , Sorry if i am asking a wrong question. Is it possible to analyse asp.net mvc/web api  using perfview.

  2. In a word, Yes.   See channel9.msdn.com/…/Tutorial-14-Investigating-Wall-Clock-responce-time-in-ASPNET-Scenarios for some more information.   But in general you can investigate pretty much any performance problem on windows to at least some degree (and often it is a very high degree), using PerfView.

  3. Ben says:

    Hello Vance, thinking out loud here, but as a newbie, what would really help me is a "State of ETW" page somewhere, that is updated from time to time, with the 'big picture' of how the various bits fit together, and the subtleties. (SLAB, MS.D.Tracing vs System.D.Tracing, the n different tools etc.).

    I know there have been posts, documents, videos, but given that ETW is 'old' technology, it's sometimes difficult to know if the information from 3, 4, 5, years ago is still current.

    (An example: I tried rebuilding SLAB to work with MS.D.Tracing – as suggested in the notes from the latest version – but discovered that newer versions of MS.D.Tracing have an EventSourceSettings enum which conflicts with EventSourceSettings class in SLAB…)

    I guess it could just something as simple as a markdown file on github…

    Given that you appear to be the de facto high priest of ETW 🙂

    Thanks.

  4. It certainly would be nice.   I will see what I can do, but frankly it may be a while, since there are other things on my todo list (like open sourcing TraceEvent and PerfView), that have been waiting longer.  

    In your particular example above, this is likely that SLAB has just not been kept up to date.   While having an overview page might help get the big picture, it is not likely to help with things like that (which are basically 'just bugs').  

    However I will see if I can't devote a small amount of time per week to building up some Wikipeida pages, but event that will probably wait until the end of the month since I want to publish and post a few things about PerfView first…

  5. Ben says:

    Thanks Vance, your output here is prodigious by anyone's standards. And the fact that you're still answering individual questions too.

    The way I imagined the overview page, I think it might help: for example, what is probably obvious to you, but not to me, is *why* SLAB has not been kept up to date: is it because it's becoming 'abandonware'? or because the two teams don't communicate enough? Or because they don't have the same development goals or cycles…?

    I'm not saying you should hang out the dirty washing, but it would be useful to know the 'dependencies' between these technologies, how they are interrelated. And also what the expected compatibilities might be (the way I imagine it, there is a System.D.Tracing 'branch' and a Microsoft.D.Tracing 'branch', and some things only really work on one side or the other?).

    Anyway, now I'm off to read up on PerfView command line parameters to try and get it monitoring my service in production 🙂

  6. KRopa says:

    This is fantastic, thanks for this excellent tool and the video tutorials. I'll be looking forward to 1.9.

  7. Version 1.9 of PerfView is now out in the download center.  

Skip to main content