The profiler did not find any methods with source code

tom103

I'm trying to profile a Windows Store application, but ANTS Performance profiler only shows methods named "<Unknown>.<Unknown>()".

I've seen this page, but all it says about Windows Store apps is this:

Profiling Windows Store Applications with trivial methods

When profiling Windows Store Applications, some methods may not appear in profiling results because ANTS Performance Profiler ignores trivial methods for Windows Store Applications.

A method is trivial if it is smaller than 192 bytes of IL, doesn't contain any branches or loops, and doesn't contain any calls to other methods.

But it doesn't help, because the methods I'm trying to debug are not trivial...



How can I fix it?

(btw, my app is compiled as Debug, and the pdb files are present in the executable folder ; I'm starting the profiler by using the "Profile Performance" command in the ANTS menu of Visual Studio)

James B

What happens if you run the profiler and then profile your app by picking the Windows Store option on the startup screen- any different?

tom103

Hi James, thanks for your reply.

It doesn't seem to change anything, I get the same results as before.

James B

Ok - it seems that seeing <Unknown>.<unknown> has cropped up intermittently before- we have a bug ref. PP-1710 for it, but there's no indication of cause on there. I'll follow up with the APP team to see if I can find out more...

James B

Out of interest, what kind of spec is the machine you're running on? It sounds like the problem is more likely to manifest itself on lower-specification machines.

tom103

james.billings wrote:

Out of interest, what kind of spec is the machine you're running on? It sounds like the problem is more likely to manifest itself on lower-specification machines.

Windows 8 Pro 64-bit
Intel Core i7 2600 3.4GHz
8GB RAM

James B

Hmm, that doesn't sound too shoddy...

James B

Is there any possibility we'll be able to obtain a copy of your code (or if that's not possible, at least the executables) so we can investigate further? So far, this problem hasn't been reliably reproducible in-house.

tom103

james.billings wrote:

Is there any possibility we'll be able to obtain a copy of your code (or if that's not possible, at least the executables) so we can investigate further? So far, this problem hasn't been reliably reproducible in-house.

I can't send you the code of this specific application because it belongs to my company, but I can reproduce the issue with any Windows Store app...

This project has the problem; I created it from the Grid App (XAML) template and didn't change anything in it.

James B

Thanks- we'll take a look. Interesting you say any Store app does it, as we've tested various ones here without problem; so it may still prove to be environmental rather than application specific. I'll post back when I have an update.

nitin3381

I am also facing same issue, Let me know if there is any solution or work around.