Skip to content

[Net6] dotnet trace profiling yields to mangled/empty frame names #6178

Closed

Description

Steps to Reproduce

  1. Building a net6.0-android uno app, with net6 android workload installed, which the following:
<PropertyGroup>
	<IsEmulator Condition="'$(IsEmulator)' == ''">true</IsEmulator>
	<AndroidEnableProfiler>true</AndroidEnableProfiler>
	<AndroidLinkResources>true</AndroidLinkResources>
</PropertyGroup>
	
<ItemGroup>
	<AndroidEnvironment Condition="'$(IsEmulator)' == 'true'" Include="Android\environment.emulator.txt" />
	<AndroidEnvironment Condition="'$(IsEmulator)' != 'true'" Include="Android\environment.device.txt" />
</ItemGroup>

Sample repro: net6profiletest.zip

  1. Run dotnet-dsrouter client-server -tcps 127.0.0.1:9001 -ipcc /tmp/my-app --verbose debug
  2. Run dotnet-trace collect --diagnostic-port /tmp/my-app --format speedscope -o my-app-trace
  3. Go to the net6profiletest.Mobile folder of the repro app
  4. Start the app with dotnet build -f net6.0-android -t:run -c Release -p:IsEmulator=true
  5. Wait for the app to start, then stop dotnet-trace
  6. Load the resulting file in speedscope.app

Expected Behavior

Frames in speedscope are readable.

Actual Behavior

image

Version Information

6.0.100-preview.7.21379.14

Log File

my-app-trace.speedscope.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Labels

Area: Mono RuntimeMono-related issues: BCL bugs, AOT issues, etc.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions