Profiler showing wrong coroutine name

I’m having a problem where the profiler appears to show a random coroutine name with massive performance cost. The thing is, i already identified the correct coroutine which was causing the behavior which was completely independent from the one shown in the profiler. Further, disabling the wrongly shown coroutine makes the profiler show a different random one which is also not related to said behavior.

The only way to get the correct coroutine name is to use deep profiling, which for performance reasons doesn’t really work. (needs like 20 seconds to expand the tree)

Does anyone know how this might be caused?

I agree. This is an issue that always happen. You should report a bug.

I have also found this to be true. Regular profiling combines calls to like coroutines on different types on one line and labels it with the object type of one of the objects, implying that all calls are occurring on that object type.

Deep profiling still combines the like coroutines (which I guess I can understand as they are all run on the same base type) but labels it in a less misleading way → d__16.System.Collections.Ienumerator.get_Current()

This bug still occur! (2017.3.0f3 Personal)