Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Created attachment 11495 [details]
Profiler version 0.15 consistently opens and goes through deploying the app on the emulator or physical device but does not start profiling even after clicking on the start profiling button or file menu. Debugging the app via emulator or physical device works as expected.
I'm not able to reproduce your scenario.
Could you please confirm which version of Visual Studio or Xamarin Studio you are using on Windows?
Could you please also attach a screenshot of the Profiler after it launches.
Also using the Process Explorer, as per this example, http://superuser.com/questions/415360/how-do-i-find-out-command-line-arguments-of-a-running-program, could you also confirm what parameters were used to start the Xamarin Profiler process.
Created attachment 11527 [details]
Process explorer screenshot of profiler after running from Xamarin
Created attachment 11528 [details]
Screenshot of profiler running from Xamarin
Is StartActivity the only activity marked as "MainLauncher = true"?
Also the profiler.log you posted originally, can you confirm this was taken by going to "Help->Open Log Directory" inside the Profiler, then re-ordering the log files to most recent at the top, then that log file was the one attached?
Apologies if this is obvious, I just want to make sure everything is covered.
1. Yes, StartingActivity is the only activity marked MainLauncher = true.
2. Yes, that was the most current log at that point. To double check I opened the profiler again and went "Help->Open Log Directory" and attached the result.
Created attachment 11533 [details]
Current profiler log
Sure can you allow me to remote in?
I'm around for the next 4 hours.
I have TeamViewer.
I'm around from 10am GMT until 7-8pm GMT. most days.
OK I'll be available at 7PDT today.
Great news. I've just tested the latest Alpha release myself and Android profiling was fixed by the runtime team. You can grab it from the Alpha channel.
It should work with the latest 0.16 Profiler release. So you could try to switch to this latest Alpha, but keep in mind it is an Alpha of Android and iOS. I suggest being ready to roll-back to the latest Beta or Stable if you notice anything unusual happening in your app.
I will close this issue for now, but re-open it if profiling is still not working for you.
I got 0.16 to profile once on an emulator. I cannot get it to profile again on the same emulator or a physical device. If I need to start this as a separate bug report let me know. The profiler opens fine but crashes immediately upon opening.
I will attach a zip file of the successful and unsuccessful runs on 0.16.
Created attachment 11581 [details]
0.16 profiler logs and error screen
@orion Is this error happening with the latest Alpha, or just with the latest 0.16 and a previous Beta/Stable?
With the latest alpha. I switched XS to the alpha channel and left it there.
I have checked this issue with latest Alpha Xamarin builds (XS 22.214.171.124 + XVS 3.11.658) and Xamarin Profiler 0.16.0.0, is working fine for me. Please refer the screencast : http://www.screencast.com/t/YLcRlXc6iN38
@orion could you please check this with latest Alpha channel builds and let us know if you are still getting this issue.
Can I organise another Team meeting session with you next week? Let me know which day works for you.
Does Monday @ 7:00am PDT work for you?
Are you in this morning or what day works for you?
Sorry I've been ill Ryan. Will you be around tomorrow morning?
Yes. Tomorrow at 7:00 am PDT would work for me. Does that suit you?
Yes that works Ryan.
Ryan, let me know when you are ready.
Tester confirm it works for them on Windows 7. They haven't installed Windows 10 yet, so can't confirm on there yet.
Are you logged into your machine as a used called "Office"?
Can you please confirm that the location "C:\Users\Office\AppData\Local\Temp\" exists on your HD?
the last thing I can think of, is it might be the device. Can you borrow another Android device and try that?
One of the other team members sending use the latest logcat.
I'd suggest clearing it first.
1. Clear logcat "adb logcat -c"
2. Pipe logcat to a file "adb logcat -d > logcat.txt"
3. try profiling on device.
4. Upon failure send us the logcat.
I'm not 100% convinced this will reveal anything new, but it is worth a try.
Don't clear the log, the profiler already does that. Just profiling from the profiler, and when done, copy/paste the contents of the Console view in the profiler, which contains the logcat for the duration of the profile run
Created attachment 11709 [details]
Screenshot #1 No console tab in profiler and runtime error
Created attachment 11710 [details]
Screenshot #2 Console tab shows up only when connected to live profiling session
I tried a different device and the behavior was the same. Immediate crash and unable to get it to start by killing app and manually restarting the profiling from the triangle button.
The console tab in the profiler never was visible when I was trying to profile with any physical device.
What is the contents of the Console Tab that that point? Is anything written to it?
When the app crashes on the physical device there is no console tab in the profiler.
As of profiler version 0.17 and the latest stable Xamarin Studio build I am able to profile on both emulator and physical device.
Thanks @Ryan for the confirmation.
As per comment 46, I am closing this issue.