Search Issue Tracker

Fixed in 2022.1.X

Fixed in 2021.2.X



Found in




Issue ID




[Behavior change] mono_debug_find_method returns non-null object for not compiled methods



Steps to reproduce:
1. Download the attached "" project
2. Open the Trade scene
3. Open profiler, activate "Call Stacks" with GC.Alloc option
4. Enter play mode and wait for a few frames to be recorded
5. Pause the game
6. Select the first frame
7. In the Timeline view of the profiler look through Magenta tiles called "GC.Alloc"

Expected result: The stack trace shows the correct stack for the allocation.
Actual result: The top line of the stack trace is unrelated

Reproducible with: 2021.2.0a18, 2021.2.0b7, 2022.1.0a5
Not reproduce with: 2019.4.29f1, 2020.3.16f1, 2021.1.17f1, 2021.2.0a17

Incorrect stack traces:

This is a sibling of bug which I've created to track mono behavior change.

The core issue is that mono_debug_find_method started returning non NULL data for methods which are not compiled. The old behavior is much more preferred as it saves useless allocation deallocation IMHO

I've added an extra null check in the PR
but for profiler it would be much more performant to avoid any allocs.

Please see for the repro project and more information

  1. Resolution Note (fix version 2022.1):

    Fixed memory leak that occurred when mono_debug_find_method could not find the requested method.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.