Memory Profiling Freezes on Taking Capture (MacOS Apple Silicon)

Unity Engine
, ,
1

Hi,

I’m trying to use the Memory Capture package in Unity 6 .9f1 to be precise (upgraded when .4 had the same issue).

When I press Take Snapshot it opens the Memory Capture progress window and then freezes unity.
I have plenty of available memory and there isn’t much CPU activity.

The project is very small, 20 odd source files and a few scriptable objects.

Editor log isn’t showing much. The last entries are:

2024-07-05 19:50:29.261 Unity[68773:13264428] CAMetalLayer ignoring invalid setDrawableSize width=0.000000 height=0.000000
2024-07-05 19:50:29.263 Unity[68773:13264428] CAMetalLayer ignoring invalid setDrawableSize width=0.000000 height=0.000000
2024-07-05 19:50:31.407 Unity[68773:13264428] CAMetalLayer ignoring invalid setDrawableSize width=0.000000 height=0.000000
2024-07-05 19:50:31.408 Unity[68773:13264428] CAMetalLayer ignoring invalid setDrawableSize width=0.000000 height=0.000000
2024-07-05 19:50:31.713 Unity[68773:13264428] CAMetalLayer ignoring invalid setDrawableSize width=0.000000 height=0.000000
2024-07-05 19:50:31.720 Unity[68773:13264428] CAMetalLayer ignoring invalid setDrawableSize width=0.000000 height=0.000000
MemoryCapture: Header Serialization : 0 ms
MemoryCapture: Waiting for current load operation to finish : 0 ms
MemoryCapture: Metadata Serialization : 0 ms
MemoryCapture: Capture flags Serialization : 327 ms
MemoryCapture: Managed Heaps : 1192 ms

Let me know if there’s any other information I can provide.

Thanks.

1 Like
2

Hello,
Please report a bug (Editor Menu: Help > Report a Bug) with the project attached. We’ll need it to figure out what’s going wrong here. It’s been a while since we’ve heard of capture being broken and I have no clue why it’d break now… :confused:

3

Thanks,
I’ve submitted a bug with the ID IN-79961

2 Likes
4

thanks for filing a bug @TheRobWatling - the project was really helpful!
we’ve found the reason and are backporting the fix now
we needed to do a few changes in mono to avoid types initialization during the capture - that was causing the deadlock

2 Likes