Skip to content

[.NET10] Epic: Investigate paths to help users be more successful discovering memory and layout issues #28874

Open
0 of 3 issues completed
@PureWeen

Description

@PureWeen

Description

We are in the process of investigating various paths to help users better locate memory issues and narrow down performance bottlenecks.

We will update this issue with sub items as the discussion continues.

Areas to Investigate

  • OpenTelemetry
    • Can we expose information about leaking types and performance issues through Telemetry? Nalu Framework has a really good example how to add some leak tracking to keep track if your pages are leaking
  • Make it easier for users to generate dump files and speedscopes

Sub-issues

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-architectureIssues with code structure, SDK structure, implementation detailss/triagedIssue has been reviewedt/perfThe issue affects performance (runtime speed, memory usage, startup time, etc.) (sub: perf)

    Type

    No type

    Projects

    Status

    Todo

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions